Fix Version/s: None
When having a big number of vnodes (such as 256/node advised by http://www.datastax.com/dev/blog/upgrading-an-existing-cluster-to-vnodes), using secondary indices becomes really slow because Cassandra has to search for the index in all the nodes.
This results in very slow queries (in the order of 1-2s).
For an exemple, see this tracing with a 3 physical nodes cluster with 256 vnodes on each.
The keyspace has a RF=3.
|Workflow||patch-available, re-open possible [ 12753800 ]||reopen-resolved, no closed status, patch-avail, testing [ 12758984 ]|
|Workflow||no-reopen-closed, patch-avail [ 12746103 ]||patch-available, re-open possible [ 12753800 ]|
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Duplicate [ 3 ]|