-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Shared mode consumer priority #134
Comments
|
the consumer may be assigned different priority based on the machine's capacity or location(e.g. rack or idc). |
That was what I had in mind as well. My other question would be: would anyone need in practice more that 2 priorities ( |
Currently we only require 2 priorities in the applications, but I think it's better to have the ability to have multiple priorities. |
* adding user acking and fixing bugs * cleaning up
optimize for apache#134 including the following aspects: recordToEntry paralleled publish message to bookie asynchronous In our environment, produce delay is about one-fifth of the previous
Shared mode consumer priority, the messages will only goes to the consumers with higher priority if there's permit, otherwise the message can also be pushed to the consumers with lower priority.
[merlimat]
Good idea. This should be relatively easy to implement.
[DongbinNie]
:-)
The text was updated successfully, but these errors were encountered: