[
https://issues.apache.org/jira/browse/ZOOKEEPER-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895818#comment-13895818
]
Rakesh R commented on ZOOKEEPER-1872:
-------------------------------------
Yes I agree. +1 for 3.4 fixing and will do trunk failure analysis separately.
In trunk, probably some more places it needs cleanup of the server. In normal
run it should get IOException when establishing connection and would fail. Just
to confirm my understanding can you please run the test alone and see its
passing?
> 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: LeaderSessionTrackerTest-output.txt,
> ZOOKEEPER-1872.patch, ZOOKEEPER-1872.patch, ZOOKEEPER-1872.patch,
> ZOOKEEPER-1872.patch, ZOOKEEPER-1872.patch, ZOOKEEPER-1872.patch,
> ZOOKEEPER-1872.patch, ZOOKEEPER-1872.patch, ZOOKEEPER-1872.patch,
> ZOOKEEPER-1872.patch, ZOOKEEPER-1872_br3_4.patch, ZOOKEEPER-1872_br3_4.patch,
> stack-trace.txt
>
>
> 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)
