[jira] [Commented] (ZOOKEEPER-1794) Add hash check to transaction history in quorum servers

["Alexander Shraer (JIRA)" <ji...@apache.org>]

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

Alexander Shraer commented on ZOOKEEPER-1794:
---------------------------------------------

[~abranzyck] wrote "Not ready for review yet, no tests included." has this changed ?

BTW, I like the idea of this patch, would be nice to have it in. It seems though that computing and checking hashes for every operation may affect performance, so part of the testing should probably be running the system tests and examining performance.


> 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
>    Affects Versions: 3.5.0
>            Reporter: Germán Blanco
>            Assignee: Germán Blanco
>             Fix For: 3.5.0
>
>         Attachments: ZOOKEEPER-1794.patch, ZOOKEEPER-1794.patch, ZOOKEEPER-1794.patch
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> The goal of this task is to add a hash number to each transaction in the transaction history. This hash number will depend on the entire 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, during the broadcast phase. The hash number will be checked by the leader when learners try to connect, and it shall also be sent together with the snapshot during synchronisation. If the hash number does not match, the synchronisation shall be done with a snapshot in order to overwrite the conflicts in the transaction history.



--
This message was sent by Atlassian JIRA
(v6.2#6252)