Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Messenger] More on unique Redis consumer names #14888

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.

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
Apr 21, 2021

Conversation

danmichaelo
Copy link
Contributor

I managed to miss the warning that the (strem,group,consumer) combination must be unique. I think it would make it less easy to miss if it was also mentioned in the Supervisor section, so I've tried to add a mention of it there. I also expanded the original warning block a bit.

There are many different combinations of transports and ways to manage workers, so I understand that the docs should not delve too deep into each one, but I think it's worthwhile to cover the Redis + Supervisor combo quite well, since it's one of the easier combinations to get started with, which also can work really well. Let me know what you think.

Related: #11869 #35358

@alexsegura
Copy link

This PR helped me a lot to understand the problem with unique Redis consumer names 👍

When using Supervisor, it's super useful to have this documented, indeed.

@javiereguiluz javiereguiluz added this to the 5.2 milestone Apr 21, 2021
@javiereguiluz javiereguiluz merged commit ce2b086 into symfony:5.2 Apr 21, 2021
@javiereguiluz
Copy link
Member

Thanks @danmichaelo!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants