[ROCKETMQ-298] A topic’s readQueueNums and writeQueueNums could be different, which could cause some potential problem

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: rocketmq-client, rocketmq-tools
• Assignee: Xiaorui Wang
• Reporter: Mark Yang
• Created: 03/Oct/17 09:30
• Updated: 03/Oct/17 09:30

Description

1 If readQueueNums is bigger than writeQueueNums, some consumer in clustering mode could never receive messages.
2 If writeQueueNums is bigger than readQueueNums, some messages could never be consumed.
And borker needs to keep max(readQueueNums, writeQueueNums) in each situation.

So different read and write queue numbers really necessary? Does anyone have a production use case for this?
If not, we should consider to combine the two parameters to one.