GitHub user GenerousMan added a comment to the discussion: DLedgerControlller模式可以保证消息一致性吗
If you have the allAckInSyncStateSet switch turned on, then no, a replica node that is significantly behind will not be chosen as primary upon startup. If a node is in the syncStateSet and then gets elected as primary, there is actually no data loss even if log truncation occurs at this point. This is because this portion of data has not been successfully transmitted - it has not been acknowledged by all the nodes in the syncStateSet. GitHub link: https://github.com/apache/rocketmq/discussions/7691#discussioncomment-7915162 ---- This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
