Re: Cassandra crashed - possible JMX threads leak

2010-10-26 Thread Norman Maurer
Depending on finalize() is really not want you want todo, so I think the API change would be preferable. Bye, Norman 2010/10/26 Bill Au : > I would be happy to submit a patch but is it a bit more trickier than simply > calling JMXConenctor.close().  NodeProbe's use of the JMXConnector is not > e

Re: Cassandra crashed - possible JMX threads leak

2010-10-26 Thread Bill Au
I would be happy to submit a patch but is it a bit more trickier than simply calling JMXConenctor.close(). NodeProbe's use of the JMXConnector is not exposed in its API The JMX connection is created in NodeProbe's constructor. Without changing the API, the only place to call close() would be in

Re: Cassandra crashed - possible JMX threads leak

2010-10-22 Thread Jonathan Ellis
Is the fix as simple as calling close() then? Can you submit a patch for that? On Fri, Oct 22, 2010 at 2:49 PM, Bill Au wrote: > Not with the nodeprobe or nodetool command because the JVM these two > commands spawn has a very short life span. > > I am using a webapp to monitor my cassandra clust

Re: Cassandra crashed - possible JMX threads leak

2010-10-22 Thread Bill Au
Not with the nodeprobe or nodetool command because the JVM these two commands spawn has a very short life span. I am using a webapp to monitor my cassandra cluster. It pretty much uses the same code as NodeCmd class. For each incoming request, it creates an NodeProbe object and use it to get get

Re: Cassandra crashed - possible JMX threads leak

2010-10-20 Thread Frank LoVecchio
Ah, missed that. Thanks Aaron. On Wed, Oct 20, 2010 at 11:49 PM, Aaron Morton wrote: > Sounds like the problem discussed here > http://wiki.apache.org/cassandra/Operations?highlight=(allocate)|(memory) > > >

Re: Cassandra crashed - possible JMX threads leak

2010-10-20 Thread Aaron Morton
Sounds like the problem discussed here http://wiki.apache.org/cassandra/Operations?highlight=(allocate)|(memory)If you have the JNA jar it should work http://www.mail-archive.com/user@cassandra.apache.org/msg06284.htmlhttp://www.riptano.com/blog/whats-new-cassandra-065AaronOn 21 Oct, 2010,at 06:29

Re: Cassandra crashed - possible JMX threads leak

2010-10-20 Thread Frank LoVecchio
I have a cluster of 3 0.7 beta 2 nodes (built today from the latest trunk) running on Large, EBS-backed, x64 EC2 instances; RF=3. I attempted to write somewhere near 500,000 records every 15 minutes from a total of 5 different computers (using Pelops and multi-threading). Though my network blew

Re: Cassandra crashed - possible JMX threads leak

2010-10-20 Thread Jonathan Ellis
can you reproduce this by, say, running nodeprobe ring in a bash while loop? On Wed, Oct 20, 2010 at 3:09 PM, Bill Au wrote: > One of my Cassandra server crashed with the following: > > ERROR [ACCEPT-xxx.xxx.xxx/nnn.nnn.nnn.nnn] 2010-10-19 00:25:10,419 > CassandraDaemon.java (line 82) Uncaught ex