[ https://issues.apache.org/jira/browse/ZOOKEEPER-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008608#comment-13008608 ]
Vishal K commented on ZOOKEEPER-880: ------------------------------------ Hi Ben, The patch might fix ZOOKEEPER-939. However, ZOOKEEPER-939 does not describe how they ran into this situation (and has not attached logs). ZOOKEEPER-939 can be closed if the problem is not seen after this patch. -Vishal > QuorumCnxManager$SendWorker grows without bounds > ------------------------------------------------ > > Key: ZOOKEEPER-880 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-880 > Project: ZooKeeper > Issue Type: Bug > Affects Versions: 3.4.0 > Reporter: Jean-Daniel Cryans > Assignee: Vishal K > Priority: Blocker > Fix For: 3.4.0 > > Attachments: TRACE-hbase-hadoop-zookeeper-sv4borg9.log.gz, > ZOOKEEPER-880-3.3.patch, ZOOKEEPER-880.patch, ZOOKEEPER-880.patch, > ZOOKEEPER-880.patch, ZOOKEEPER-trunk-880, > hbase-hadoop-zookeeper-sv4borg12.log.gz, > hbase-hadoop-zookeeper-sv4borg9.log.gz, jstack > > > We're seeing an issue where one server in the ensemble has a steady growing > number of QuorumCnxManager$SendWorker threads up to a point where the OS runs > out of native threads, and at the same time we see a lot of exceptions in the > logs. This is on 3.2.2 and our config looks like: > {noformat} > tickTime=3000 > dataDir=/somewhere_thats_not_tmp > clientPort=2181 > initLimit=10 > syncLimit=5 > server.0=sv4borg9:2888:3888 > server.1=sv4borg10:2888:3888 > server.2=sv4borg11:2888:3888 > server.3=sv4borg12:2888:3888 > server.4=sv4borg13:2888:3888 > {noformat} > The issue is on the first server. I'm going to attach threads dumps and logs > in moment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira