cserwen commented on issue #7355: URL: https://github.com/apache/rocketmq/issues/7355#issuecomment-1733118782
> > > > Why not recover from the minimum cmq physical offset when abnormally exiting🤔? > > > > > > > > > collect all consumer queue last message's commit log physical offset, and use the minimum as the reputService's reputFromOffset(now is the maxPhysicalPosInLogicQueue). > > > > > > @suopovate Emmm, looks like this is the first way I mentioned. > > Maybe, I think my way is the simplest, just change the 'reputFromOffset' value, finally the data will be normal, and no data loss.🤓 > > We needn't not keep the cache of consumer queue flushed offset. @suopovate - In fact, this also has some disadvantages. Some queues may only generate a few messages, which means that its endOffset is very small. In this case, we will rebuilding almost all cqs. - By the cache, we can add the dimension of time to more reasonably determine the offset which the broker should begin to recover at. -- 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]
