[
https://issues.apache.org/jira/browse/ZOOKEEPER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774386#comment-13774386
]
Germán Blanco commented on ZOOKEEPER-87:
----------------------------------------
I made (at least) two mistakes above:
- If there are no proposals (idle ZooKeeper), then this thing is not idle
("doing nothing" as in NOT_STARTED) it is in WAITING_FOR_PROPOSAL, returning
always true for check and ready to be updated with a new proposal.
- "since we check the timeout every 1/2 tickTime", means half a ticktime needs
to be added, not half a "syncLimit * tickTime". So actually the "longest time
between a proposal and its ACK " is (((2 * syncLimit) + 1/2) * tickTime)
... isn't there a way to edit comments after one posts them?
> Follower does not shut itself down if its too far behind the leader.
> --------------------------------------------------------------------
>
> Key: ZOOKEEPER-87
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-87
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
> Affects Versions: 3.5.0, 3.4.5
> Reporter: Mahadev konar
> Assignee: Germán Blanco
> Priority: Critical
> Labels: patch
> Fix For: 3.5.0, 3.4.6
>
> Attachments: ZOOKEEPER-87_3.4.patch, ZOOKEEPER-87.patch
>
>
> Currently, the follower if lagging behind keeps sending pings to the leader
> it will stay alive and will keep getting further and further behind the
> leader. The follower should shut itself down if it is not able to keep up to
> the leader within some limit so that gurantee of updates can be made to the
> clients connected to different servers.
--
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
