cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: nodetool causing OOM?
Date Wed, 19 May 2010 06:16:03 GMT
Yeah, there's really not a whole lot we can do about these Thrift
problems other than get Avro ready as a replacement, which we are
doing. :(

On Mon, May 17, 2010 at 2:37 PM, Nahor <nahor.j+gmane@gmail.com> wrote:
> On 2010-05-17 12:51, Brandon Williams wrote:
>>
>> On Mon, May 17, 2010 at 2:44 PM, Ronald Park <ronald.park@cbs.com
>> <mailto:ronald.park@cbs.com>> wrote:
>>
>>    Hello,
>>
>>    We are getting our feet wet with Cassandra and have a test
>>    environment set up to do some heavy data insertion. [Heavy is
>>    relative: we are talking about 1M inserts in a 3 hours test.
>>
>>    Twice while running these tests, when we've tried to use
>>    'nodetool' about an hour or so into the test, to run a command
>>    like 'info' or 'tpstats' and the Cassandra node we attached to
>>    raised OOM error.
>>
>>
>> Does it only happen under load, or does it also OOM when idle?  If the
>> latter, it sounds like you're connecting it to the thrift port instead of
>> the jmx port, which would trigger
>> https://issues.apache.org/jira/browse/THRIFT-601
>>
>
> Same bug but a different way to trigger it: mixing framed and non-framed
> transport.
> I had switched a node to use framed transport to look at Chiton but didn't
> change the nodetool configuration.
>
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com

Mime
View raw message