Re: connections remain on CLOSE_WAIT state after process is killed after upgrade to 2.0.15

2015-06-22 Thread Paulo Ricardo Motta Gomes
For the record: https://issues.apache.org/jira/browse/CASSANDRA-9630 On Mon, Jun 15, 2015 at 7:19 PM, Paulo Ricardo Motta Gomes < paulo.mo...@chaordicsystems.com> wrote: > Just a quick update, I was able to fix the problem by reverting the patch > CASSANDRA-8336 in our custom cassandra build. I d

Re: connections remain on CLOSE_WAIT state after process is killed after upgrade to 2.0.15

2015-06-15 Thread Paulo Ricardo Motta Gomes
Just a quick update, I was able to fix the problem by reverting the patch CASSANDRA-8336 in our custom cassandra build. I don't know the root cause yet though. I will open a JIRA ticket and post here for reference later. On Fri, Jun 12, 2015 at 11:31 AM, Paulo Ricardo Motta Gomes < paulo.mo...@cha

connections remain on CLOSE_WAIT state after process is killed after upgrade to 2.0.15

2015-06-12 Thread Paulo Ricardo Motta Gomes
Hello, We recently upgraded a cluster from 2.0.12 to 2.0.15 and now whenever we stop/kill a cassandra process, some other nodes keep a connection with the dead node in the CLOSE_WAIT state on port 7000 for about 5-20 minutes. So, if I start the killed node again, it cannot handshake with the node