terval.
To fix this, I can:
1) reduce number of keys - rewrite app and sacrifice balance
2) increase index_interval - hurt another column families
A question:
Are there any drawbacks for using different indexInterval for column
families
in keyspace? (suppose I'll write a patch)
2011/7/15 Andrey S
Looks like key indexes eat all memory:
http://paste.kde.org/97213/
2011/7/15 Andrey Stepachev
> UPDATE:
>
> I found, that
> a) with min10G cassandra survive.
> b) I have ~1000 sstables
> c) CompactionManager uses PrecompactedRows instead of LazilyCompactedRow
>
> So
Looks like mmaped files.
2011/7/15 Donna Li
> **
>
> All:
>
> I download JNA jar and put it to cassandra lib directory. When restart
> cassandra server, I found the physical memory highly increase. There is no
> data saved in cassandra, why so much memory used by cassandra? How can I
> decre
?
2011/7/15 Andrey Stepachev
> Hi all.
>
> Cassandra constantly OOM on repair or compaction. Increasing memory doesn't
> help (6G)
> I can give more, but I think that this is not a regular situation. Cluster
> has 4 nodes. RF=3.
> Cassandra version 0.8.1
>
>
Hi all.
Cassandra constantly OOM on repair or compaction. Increasing memory doesn't
help (6G)
I can give more, but I think that this is not a regular situation. Cluster
has 4 nodes. RF=3.
Cassandra version 0.8.1
Ring looks like this:
Address DC RackStatus State Load