[
https://issues.apache.org/jira/browse/ZOOKEEPER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639163#comment-13639163
]
Germán Blanco commented on ZOOKEEPER-87:
----------------------------------------
Hello,
I am rescueing this old isssue, since it seems to be still present.
After a few tests, it seems to me that the issue of "lagging behind" affects
transactions even more seriously. I haven't been able to find any timeout for
proposals waiting for acknowledgement, is that really the case?
I really think I must be wrong there. Otherwise, since ping handling seems to
be done in a different thread, a follower could be locked at some point that
has to do with the transaction but reply to pings and it would not be accepting
any proposals. Besides, there is no warranty on the time that a transaction
takes to be updated in all servers.
Could anybody please tell me if I have read things wrongly?
Thanks a lot,
Germán.
> 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
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Priority: Critical
> Fix For: 3.5.0
>
>
> 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
