Skip to content

[Messenger] tidy MESSENGER_CONSUMER_NAME surrounds #16457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 31, 2022
Merged

[Messenger] tidy MESSENGER_CONSUMER_NAME surrounds #16457

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion messenger.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1504,7 +1504,7 @@ sentinel_master String, if null or empty Sentinel null
There should never be more than one ``messenger:consume`` command running with the same
combination of ``stream``, ``group`` and ``consumer``, or messages could end up being
handled more than once. If you run multiple queue workers, ``consumer`` can be set to an
environment variable (like ``%env(MESSENGER_CONSUMER_NAME)%``) set by Supervisor
environment variable, like ``%env(MESSENGER_CONSUMER_NAME)%``, set by Supervisor
(example below) or any other service used to manage the worker processes.
In a container environment, the ``HOSTNAME`` can be used as the consumer name, since
there is only one worker per container/host. If using Kubernetes to orchestrate the
Expand Down