[
https://issues.apache.org/jira/browse/ZOOKEEPER-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012887#comment-13012887
]
Flavio Junqueira commented on ZOOKEEPER-1036:
---------------------------------------------
Jiangwen, It is accurate what you say about read requests, but I'm not
convinced by your argument on REVALIDATE requests. A leader creates a new
session tracker when it executes startup(), and startup() is only called once
the leader has a quorum of supporters. At least this is what I see when I look
at the Leader class. Is there anything I'm missing?
> send UPTODATE to follower until a quorum of servers synced with leader
> ----------------------------------------------------------------------
>
> Key: ZOOKEEPER-1036
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1036
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Reporter: jiangwen wei
>
> 1. current process
> when leader fail, a new leader will be elected, followers will sync with the
> new leader.
> After synced, leader send UPTODATE to follower.
> 2. a corner case
> but there is a corner case, things will go wrong.
> suppose message M only exists on leader, after a follower synced with
> leader, the client connected to the follower will see M.
> but it only exists on two servers, not on a quorum of servers. If the new
> leader and the follower failed, message M is lost, but M is already seen by
> client.
> 3. one solution
> So I think UPTODATE can be sent to follower only when a quorum of server
> synced with the leader.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
