Skip to content

Commit 865a219

Browse files
committed
Add a note about messenger:stop-workers command
1 parent 5b6ff21 commit 865a219

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

messenger.rst

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -490,8 +490,19 @@ On production, there are a few important things to think about:
490490
that they see the newly deployed code. To do this, run ``messenger:stop-workers``
491491
on deploy. This will signal to each worker that it should finish the message
492492
it's currently handling and shut down gracefully. Then, Supervisor will create
493-
new worker processes. The command uses the :ref:`app <cache-configuration-with-frameworkbundle>`
494-
cache internally - so make sure this is configured to use an adapter you like.
493+
new worker processes.
494+
495+
.. note::
496+
497+
By default, the ``messenger:stop-workers`` command uses the :ref:`cache.app <cache-configuration-with-frameworkbundle>`
498+
cache pool internally.
499+
In order to ensure there is never a conflict between pools, this pool will always
500+
have its own namespace.
501+
If you are not setting the `cache.prefix.seed` parameter and your deploy strategy
502+
involves the creation of new target directories, please note that the `cache.app`
503+
pool will use by default the value of the `kernel.project_dir` parameter as base
504+
for the namespace, which will lead to different namespaces between deploys,
505+
making this command obsolete.
495506

496507
Prioritized Transports
497508
~~~~~~~~~~~~~~~~~~~~~~

0 commit comments

Comments
 (0)