[
https://issues.apache.org/jira/browse/ZOOKEEPER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Germán Blanco updated ZOOKEEPER-87:
-----------------------------------
Attachment: ZOOKEEPER-87.patch
Yet a different approach.
This patch doesn't keep a list of all pending transactions for a Learner. It
just keeps track of one transaction and makes sure that this transaction makes
it on time. When the ACK for this transaction arrives, it picks anotherone. In
the worst case there could be a delay of 2*syncLimit in one transaction, but it
is a very cheap (in terms of processing time) way to ensure that the lagging
doesn't get out of hand.
> 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.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
