See https://issues.apache.org/jira/browse/CASSANDRA-10414 for an overview
of why vnodes are currently less efficient for secondary index queries.
On Tue, Sep 29, 2015 at 12:45 PM, Robert Coli wrote:
> On Tue, Sep 15, 2015 at 7:44 AM, Tom van den Berge <
> tom.vandenbe...@gmail.com> wrote:
>
>> R
On Tue, Sep 15, 2015 at 7:44 AM, Tom van den Berge <
tom.vandenbe...@gmail.com> wrote:
> Read queries on a secondary index are somehow causing an excessively high
> CPU load on all nodes in my DC.
>
...
> What really surprised me is that executing a single query on this
> secondary index makes th
Read queries on a secondary index are somehow causing an excessively high
CPU load on all nodes in my DC.
The table has some 60K records, and the cardinality of the index is very
low (~10 distinct values). The returned result set typically contains
10-30K records.
The same queries on nodes in anot
