You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Germán Blanco (JIRA)" <ji...@apache.org> on 2013/10/14 08:20:42 UTC
[jira] [Updated] (ZOOKEEPER-1794) Add hash check to transaction
history in quorum servers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Germán Blanco updated ZOOKEEPER-1794:
-------------------------------------
Description: The goal of this task is to add a hash number to each transaction in the transaction history. This hash number will be the same in all members of the quorum, since it shall have the same result if the members have the same transaction history. That means that there will be no need to send any new information between members of the quorum. The hash number will be checked by the leader when learnes try to connect. If the hash number does not match, the synchronization will be done with a snashot in order to overwrite the conflicts in the transaction history.
> Add hash check to transaction history in quorum servers
> -------------------------------------------------------
>
> Key: ZOOKEEPER-1794
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1794
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: quorum
> Reporter: Germán Blanco
> Assignee: Germán Blanco
> Fix For: 3.4.6, 3.5.0
>
>
> The goal of this task is to add a hash number to each transaction in the transaction history. This hash number will be the same in all members of the quorum, since it shall have the same result if the members have the same transaction history. That means that there will be no need to send any new information between members of the quorum. The hash number will be checked by the leader when learnes try to connect. If the hash number does not match, the synchronization will be done with a snashot in order to overwrite the conflicts in the transaction history.
--
This message was sent by Atlassian JIRA
(v6.1#6144)