[
https://issues.apache.org/jira/browse/ZOOKEEPER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752401#comment-13752401
]
Germán Blanco commented on ZOOKEEPER-87:
----------------------------------------
Could anyone please comment on the proposal in the patch?
In my view it offers the following advantages against the previous proposals in
the thread:
- There is no need to modify the network protocol (adding information to PING
requests and responses).
- It solves the problem based on time difference, and not based on the number
of proposals. A limit on the number of pending proposals could still allow for
a follower to be behind in terms of time.
- It seems to map the behavior described already for syncLimit: "Amount of
time, in ticks (see tickTime), to allow followers to sync with ZooKeeper. If
followers fall too far behind a leader, they will be dropped."
> 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
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Priority: Critical
> Labels: patch
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-87_trunk.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
