[
https://issues.apache.org/jira/browse/ZOOKEEPER-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471724#comment-13471724
]
Thawan Kooburat commented on ZOOKEEPER-1559:
--------------------------------------------
I want to add that the root of this problem is from the leader. Base on the
current implementation, the leader start up and treat every txns in its txnlog
as committed. It add those txn into committedLog and the follower get
proposal/commit packet pair for those txns as part of the sync-up.
Let me know what you think, this problem is quite complicate if we don't want
to break compatibility.
> Learner should not snapshot uncommitted state
> ---------------------------------------------
>
> Key: ZOOKEEPER-1559
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1559
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: quorum
> Reporter: Flavio Junqueira
>
> The code in Learner.java is a bit entangled for backward compatibility
> reasons. We need to make sure that we can remove the calls to take a snapshot
> without breaking it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
