RongtongJin commented on issue #6205: URL: https://github.com/apache/rocketmq/issues/6205#issuecomment-1447669712
> branch：develop > > LitePullConsumer uses org.apache.rocketmq.client.impl.consumer.DefaultLitePullConsumerImpl#pull to get messages from the server. I found that the CommunicationMode in pullSyncImpl is SYNC. For DefaultPullConsumer, it supports both synchronous and asynchronous pull messages . In DefaultLitePullConsumer#pullThreadNums = 20 for client default configuration, and if the number of partitions/queues assigned to the client is greater than 20 at this time, since the client's long polling has not been returned by the server, it is assumed that the message is sent to a partition without long polling on the server, and the message will be delayed at this time. > > suggest：LitePullConsumer support async pull message, using asynchronous communication to get messages. > > The above is what I found after reading the code. Is this the behavior correct? Good catch! Could you subbmit a pull request to fix the issue? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
