complone commented on issue #5307: URL: https://github.com/apache/rocketmq/issues/5307#issuecomment-1279884285
Hello, I think it is necessary to enable the configuration here. The scenario used by this configuration is that when the message is written, the system has a thread that can do some other logic to the message. For example: build indexes, consume queues, notify long pull client requests. The thread will maintain a message index, and compare this index with the maximum offset of the current maximum written message to get whether there is a message that needs to be processed. When the system restarts, it will be based on duplicationEnable to decide whether to process the message from the beginning or only process the new message. When duplicationEnable is true, you also need to set CommitLog.confirmOffset to process the message from the beginning, because by default, CommitLog.confirmOffset and ReputMessageService.reputFromOffset are equal after the system is started. For details, see the code ReputMessageService.doReput. -- 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]
