> For JVM Heap it is 2G
Try 4G
> and gc_grace = 1800
Realised that I did not provide a warning about the implication this has for
node tool repair. If you are doing deleted on the CF you need to run nodetool
repair every gc_grace seconds.
In this case I think you main problem was not enough
Thanks for you reply. we will try both of your recommentation. The OS
memory is 8G， For JVM Heap it is 2G, DeletedColumn used 1.4G which are
rooted from readStage thread. Do you think we need increase the size of JVM
Heap?
Configuration for the index columnFamily is
create column family purge
You need to provide some details of the machine and the JVM configuration. But
lets say you need to have 4Gb to 8GB for the JVM heap.
If you have many deleted columns I would say you have a *lot* of garbage in
each row. Consider reducing the gc_grace seconds so the columns are purged more
freq
hmm.. did you managed to take a look using nodetool tpstats? That may give
you indication further..
Jason
On Thu, Mar 7, 2013 at 1:56 PM, 金剑 wrote:
> Hi,
>
> My version is 1.1.7
>
> Our use case is : we have a index columnfamily to record how many resource
> is stored for a user. The number m
Hi,
My version is 1.1.7
Our use case is : we have a index columnfamily to record how many resource
is stored for a user. The number might vary from tens to millions.
We provide a feature to let user to delete resource according prefix.
we found some cassandra will OOM after some period. The
