[
https://issues.apache.org/jira/browse/ZOOKEEPER-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012841#comment-13012841
]
jiangwen wei commented on ZOOKEEPER-1036:
-----------------------------------------
TO Camille Fournier:
what you said is right, but it does not solve this problem.
follower don't need forward the read requests to leader, the read requests
don't need leader's response.
REVALIDATE don't count on a quorum of servers have synced with leader.
REVALIDATED session may see the messages that not exits in a quorum of servers
in this case.
for more information, please look into the LeanerHandler class that will handle
the REVALIDATE request from followers
> 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
