Ok, I've found the answer, this is just for the record. The 100K limit is not related to 2nd index but to tombstone itself. It has been introduced recently (C* 2.0.2)
The JIRA : https://issues.apache.org/jira/browse/CASSANDRA-6117 The commit: https://github.com/jbellis/cassandra/commit/4ac18ae805d28d8f4cb44b42e2244bfa6d2875e1 Basically, whenever the tombstone count exceed a defined threshold, C* issues a TombstoneOverwhelmingException, no matter it is a normal or 2nd index column family On Sat, Mar 22, 2014 at 11:57 PM, DuyHai Doan <doanduy...@gmail.com> wrote: > Sorry, my finger slipped on "enter" > > So as I said, > http://www.datastax.com/documentation/cql/3.1/cql/ddl/ddl_when_use_index_c.html > > *Problems using an index on a frequently updated or deleted column* > > Cassandra stores tombstones in the index until the tombstone limit reaches > *100K* cells. After exceeding the tombstone limit, the query that uses > the indexed value will fail. > > Does anyone has technical details about this *100K* limit ? Can someone > give me a pointer to a JIRA or some blog explaining this limitation ? > > Regards > > Duy Hai DOAN > > > On Sat, Mar 22, 2014 at 11:55 PM, DuyHai Doan <doanduy...@gmail.com>wrote: > >> Hello >> >> I've read the documentation about secondary index and among the >> use-cases to avoid, there is the case of frequenty updated/deleted columns: >> >> >
