cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mick Semb Wever <>
Subject memory problems still post- CASSANDRA-3492
Date Tue, 15 Nov 2011 21:04:24 GMT
I've got a following problem to CASSANDRA-3492, also related to
ridiculously high memory. 

After the fix yesterday for CASSANDRA-3492 I have that node in question
up and running. 

But another node (on the same machine but different cluster), even after
an upgrade to the staging 1.0.3 and a `nodetool scrub`, always soaks all
available memory (up to and plateau at 30G). In fact no cf there use
compression anymore. 

  It has been down for some days now while I was working on that other
  After it has finished startup memory just keeps growing to 30G.
Although i don't see any OOM when Xmx is set lower the node basically
becomes unusable.
  I can see in tpstats 

"HintedHandoff  (active)1    (pending)2"

 and it just seems to stay like that. 

Is there a way to more closely monitor that active hinted handoff? 
Can one hinted handoff be responsible for such heap?


"Driving ambition is the last refuge of the failure." Oscar Wilde 

| | |
|   | Java XSS Filter |

View raw message