Mahadev konar commented on ZOOKEEPER-508:

i fugured out the reason why it fails on the assertion errors != 0. The whole 
scenario of 483 fialing with truncate is this

- the test case shutdowns all the followers
- the leader does not realize that its lost the leadership, becasue the time we 
ping to see if the leader is still the leader (maybe 1 sec) is greater than the 
time hte followers actually take to shutdown and get back and in sync with the 
- so the leader never shutsdown any of its stuff (no NIO rejection or nething 

so in your case, sometimes the client conencts to the leader and will never see 
errors. On the other hand sometimes it may pas s on connection to other 
followers and your testcase will pass. So we cannot really say that your test 
case is fool proof.

> proposals and commits for DIFF and Truncate messages from the leader to 
> followers is buggy.
> -------------------------------------------------------------------------------------------
>                 Key: ZOOKEEPER-508
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-508
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: quorum
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>            Priority: Blocker
>             Fix For: 3.2.1, 3.3.0
>         Attachments: ZOOKEEPER-508.patch, ZOOKEEPER-508.patch
> The proposals and commits sent by the leader after it asks the followers to 
> truncate there logs or starts sending a diff has missing messages which 
> causes out of order commits messages and causes the followers to shutdown 
> because of these out of order commits.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to