humkum commented on issue #9307: URL: https://github.com/apache/rocketmq/issues/9307#issuecomment-2772351507
> > After investigation, it is found that when the consumption position does not exist on the broker of the server side, the server will check if the difference between the maximum position of the commitLog and the physical offset of the message corresponding to the consumption offset exceeds 40% of the memory size. If so, an exception will be thrown and the consumption offset will not be returned. > > 1. Doesn't this just show that RocketMQ has considered everything? [FYI](https://blog.csdn.net/a417930422/article/details/83585397). > 2. How long has your consumer been stalled so that messages exceed 40% of memory? > > If your consumer cannot perceive the routing change, you should investigate the consumer, not the broker. Because it is not just expansion, many situations can cause routing changes. If the consumer cannot perceive it, it will cause various problems. Not only in consumer cannot perceive the routing change. As I said, this problem will also occur when the consumer stops for a while during this period. -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
