You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2013/02/08 11:41:13 UTC

[jira] [Commented] (ZOOKEEPER-1642) Leader loading database twice

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

Flavio Junqueira commented on ZOOKEEPER-1642:
---------------------------------------------

I would be interested in the opinion of folks that have worked on this part of the code. Is there anything I'm overlooking? In any case, I'm uploading a simple preliminary patch with an idea for solving this.
                
> Leader loading database twice
> -----------------------------
>
>                 Key: ZOOKEEPER-1642
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1642
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Flavio Junqueira
>             Fix For: 3.5.0, 3.4.6
>
>         Attachments: ZOOKEEPER-1642.patch
>
>
> The leader server currently loads the database before running leader election when trying to figure out the zxid it needs to use for the election and again when it starts leading. This is problematic for larger databases so we should remove the redundant load if possible. 
> The code references are:
> # getLastLoggedZxid() in QuorumPeer;
> # loadData() in ZooKeeperServer.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira