Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
In current implementations, rocketmq consumer will allocate message queue in client itself by fetching all clientid and all mq.
While when user hopes to switch balance strategy, some problem will be suffered in the intermediate state before all client instance have been change to the same new strategy.
Say there are there clients with Strategy `AllocateMessageQueueAveragely`, when users needs to use their own `AllocateMessageQueueStrategy`, and they upgrade the client1 , and some mq will be missing to allocate or some mq allocate to multiple client instances, which will result in message duplication or message accumulation that fail to be consumed
Attachments
Issue Links
- links to
