maixiaohai commented on issue #3371: URL: https://github.com/apache/rocketmq/issues/3371#issuecomment-940937397
> > > Part B may be caused by following code > > > <img alt="截屏2021-09-24 下午5 44 22" width="1050" src="https://user-images.githubusercontent.com/3734319/134654822-c67ebfa4-0b6c-4e74-ab37-63a61ede6810.png"> > > > @odbozhou > > > > > > I will follow the above questions. > > @maixiaohai > > The retry topic processing methods of pop and push modes are completely different. The retry topic of push is consumed through client subscription. Therefore, SubscriptionData has a retry topic of push. The consumption of retry topic of pop is processed on the server side. There is a certain probability of consumption at the end, so when switching to pop mode, SubscriptionData will not have a retry topic Got it~ Just think is difficult for users to understand, and difficult for admin & sre to find the consume bottleneck~ -- 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]
