[
https://issues.apache.org/jira/browse/ZOOKEEPER-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886277#comment-13886277
]
Flavio Junqueira commented on ZOOKEEPER-1872:
---------------------------------------------
I've been noticing some strange intermittent behavior in some test cases on
jenkins, and it is possible that something like this is the root cause. For
example, testCorruption in one instance didn't even complete the setup.
The changes you propose look good, the only small change I'd like to suggest is
that since we are adding a try block, we might as well catch the exception and
fail. What do you think, [~rakeshr]?
> QuorumPeer is not shutdown in few cases
> ---------------------------------------
>
> Key: ZOOKEEPER-1872
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1872
> Project: ZooKeeper
> Issue Type: Sub-task
> Reporter: Rakesh R
> Assignee: Rakesh R
> Labels: test
> Fix For: 3.4.6, 3.5.0
>
> Attachments: ZOOKEEPER-1872.patch, ZOOKEEPER-1872.patch,
> ZOOKEEPER-1872_br3_4.patch
>
>
> Few cases are leaving quorumpeer running after the test case execution. Needs
> proper teardown for these.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
