[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790305#comment-13790305
 ] 

Germán Blanco commented on ZOOKEEPER-1777:
------------------------------------------

Could anybody help me see if this might work?
- The hash check of each transaction is stored together with the rest of 
session data.
- This hash check is sent together with the transaction response to the clients.
- Clients store the last transaction's hash check.
- Clients send the last transaction's hash check when connecting to the 
ensemble.
1 - The problem is detected when a server with wrong data tries to connect to 
the leader.
2 - Big WARN in the log.
3 - An snapshot is sent to this server, including the session data with the 
transactions' hash checks.
4 - If a client attempts to connect using a wrong transaction hash check, the 
session for that client is closed. Another WARN in the log.


> Missing ephemeral nodes in one of the members of the ensemble
> -------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1777
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1777
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: quorum
>    Affects Versions: 3.4.5
>         Environment: Linux, Java 1.7
>            Reporter: Germán Blanco
>            Assignee: Germán Blanco
>            Priority: Critical
>             Fix For: 3.4.6, 3.5.0
>
>         Attachments: logs_trunk.tar.gz, snaps.tar, ZOOKEEPER-1777-3.4.patch, 
> ZOOKEEPER-1777.patch, ZOOKEEPER-1777.patch, ZOOKEEPER-1777.tar.gz
>
>
> In a 3-servers ensemble, one of the followers doesn't see part of the 
> ephemeral nodes that are present in the leader and the other follower. 
> The 8 missing nodes in "the follower that is not ok" were created in the end 
> of epoch 1, the ensemble is running in epoch 2.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to