[
https://issues.apache.org/jira/browse/ZOOKEEPER-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898962#comment-13898962
]
Rakesh R commented on ZOOKEEPER-1872:
-------------------------------------
Hi Flavio,
I have observed the [win3.4 jenkins
reports|https://builds.apache.org/job/ZooKeeper-3.4-WinVS2008_java] 433, 434,
435. In 433 and 435 it shows good improvement, earlier it was failing very
frequently. But 434 shows sign of dirty quorumpeers, I feel still some more
corner case has to be addressed to make it stable.
bq.I have run LeaderSessionTrackerTest in isolation and it fails the same way
Yeah, today I have used windows + java7 in trunk. The test case is hanging like
the way you had mentioned. I'm doubting any behavioral change in socket
channels in java6 and java7
[~phunt] yeah should tackle trunk too
> 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.7, 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)
