Uploaded image for project: 'Apache RocketMQ'
  1. Apache RocketMQ
  2. ROCKETMQ-298

A topic’s readQueueNums and writeQueueNums could be different, which could cause some potential problem

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              vintagewang Xiaorui Wang
              Reporter:
              mark_yang Mark Yang
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: