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

["Mark Yang (JIRA)" <ji...@apache.org>]

Mark Yang created ROCKETMQ-298:
----------------------------------

             Summary: A topic’s readQueueNums and writeQueueNums could be different, which could cause some potential problem
                 Key: ROCKETMQ-298
                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-298
             Project: Apache RocketMQ
          Issue Type: Improvement
          Components: rocketmq-client, rocketmq-tools
            Reporter: Mark Yang
            Assignee: Xiaorui Wang



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.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)