[
https://issues.apache.org/jira/browse/ZOOKEEPER-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785581#comment-13785581
]
Flavio Junqueira commented on ZOOKEEPER-1558:
---------------------------------------------
You may be thinking about a different jira. This is one is not about long
transfers, but about taking a snapshot at the wrong time, which causes us to
include uncommitted state in the snapshot. This solution is not complete, but
takes care of the scenario described originally in ZOOKEEPER-1549, which is
supposed to go into 3.5.0 only (see discussion above).
I'd like to come to a resolution for this jira, so I'd appreciate if you could
either propose a different plan or review the patch, [~thawan].
> Leader should not snapshot uncommitted state
> --------------------------------------------
>
> Key: ZOOKEEPER-1558
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1558
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: quorum
> Reporter: Flavio Junqueira
> Assignee: Flavio Junqueira
> Priority: Blocker
> Fix For: 3.4.6
>
> Attachments: ZOOKEEPER-1558.patch, ZOOKEEPER-1558.patch,
> ZOOKEEPER-1558.patch, ZOOKEEPER-1558.patch
>
>
> Leader currently takes a snapshot when it calls loadData in the beginning of
> the lead() method. The loaded data, however, may contain uncommitted state.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
