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

Optimize ConsumeMessageOrderlyService by attaching MessageQueue to thread

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Feedback Received
    • None
    • 4.2.0
    • None
    • None

    Description

      The current logic of ConsumeMessageOrderlyService is using lock for each MessageQueue.

      It may block the thread pool.

      If the ConsumeRequest queue is as follows:
      q1, q1, q1, q1, q2, q2, q2
      the thread pool will block on q1, and q2 is waiting.

      If attach q1 to thread1, q2 to thread2, then q1 and q2 is consuming at the same time.

      Attachments

        Activity

          People

            zander dongeforever
            zander dongeforever
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: