Hi guys,
I am looking at added and dropped option in Cassandra between 1.2.18 and
2.0.11 and this makes me wonder:
Why has the index_interval option been removed from cassandra.yaml ? I know
we can also define it on a per table basis, yet, this global option was
quite useful to tune memory
https://issues.apache.org/jira/browse/CASSANDRA-3534
On Mon, Dec 29, 2014 at 6:58 PM, Alain RODRIGUEZ arodr...@gmail.com wrote:
Hi guys,
I am looking at added and dropped option in Cassandra between 1.2.18 and
2.0.11 and this makes me wonder:
Why has the index_interval option been removed
Thanks for the pointer Jason,
Yet, I thought that cache and memtables went off-heap only in version 2.1
and not 2.0 (As of Cassandra 2.0, there are two major pieces of the
storage engine that still depend on the JVM heap: memtables and the key
cache. --
What you are asking maybe answer in the code level and pretty deep stuff,
at least from user (like me) point of view. But to quote Jonathan
in CASSANDRA-3534, Then you will be able to say use X amount of memory for
memtables, Y amount for the cache (and monitor Z amount for the bloom
filters)
I made an error on Topic title.
We are indeed going to do it (that's why I made the mistake), but I am
speaking of 1.2 -- 2.0 here, and we will start by this before going to
2.1, since we want to do it in rolling upgrade way.
Thanks for your enlightening pointer about this vanished pressure
