[
https://issues.apache.org/jira/browse/ZOOKEEPER-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424487#comment-13424487
]
Patrick Hunt commented on ZOOKEEPER-1521:
-----------------------------------------
I verified this fix by running a very large snapshot file with the unfixed code
and initlimit=200 and synclimit=2 (ticktime = 2000 in all cases), which failed
to allow sufficient time during the init phase. I then re-ran this using the
fixed code and the quorum came up successfully.
> LearnerHandler initLimit/syncLimit problems specifying follower socket
> timeout limits
> -------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1521
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1521
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.4.3, 3.3.5, 3.5.0
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Priority: Critical
> Fix For: 3.3.6, 3.4.4, 3.5.0
>
> Attachments: ZOOKEEPER-1521.patch, ZOOKEEPER-1521_br33.patch,
> ZOOKEEPER-1521_br34.patch
>
>
> branch 3.3: The leader is expecting the follower to initialize in syncLimit
> time rather than initLimit. In LearnerHandler run line 395 (branch33) we look
> for the ack from the follower with a timeout of syncLimit.
> branch 3.4+: seems like ZOOKEEPER-1136 introduced a regression while
> attempting to fix the problem. It sets the timeout as initLimit however it
> never sets the timeout to syncLimit once the ack is received.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
