dongeforever created ROCKETMQ-232:
-------------------------------------
Summary: Optimize ConsumeMessageOrderlyService by attaching
MessageQueue to thread
Key: ROCKETMQ-232
URL: https://issues.apache.org/jira/browse/ROCKETMQ-232
Project: Apache RocketMQ
Issue Type: Bug
Reporter: dongeforever
Assignee: vongosling
Fix For: 4.2.0-incubating
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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)