of the data, it'll be much faster.
On Thu, Sep 18, 2014 at 6:33 PM, Jay Patel pateljay3...@gmail.com
wrote:
Hi there,
We are seeing extreme slow down (500ms to 1s) in query on secondary
index with vnode. I'm seeing multiple secondary index scans on a given
node in trace output when vnode
Thanks Tyler for the details. I'm still trying to understand what you
described.
Just to simplify my question what I don't understand:
When coordinator fires indexed scan request to node 192.168.51.22, why
don't it ask that node to check all of its (at least primary) ranges for
the queried
Thanks Robert for your intput but that sounds little crazy to me. Still
physical node is the same so why can't it just do one indexed scan for all
the contiguous or non-contiguous token ranges (vnodes) held by that
physical node. I doubt that it needs to respect token order for some
reason hence
(-9223372036854775808), max(-9193352069377957523)] vs.
(max(-8959555493872108621),
max(-8929774302283364912)]
Jay
On Fri, Sep 19, 2014 at 3:28 PM, Tyler Hobbs ty...@datastax.com wrote:
On Fri, Sep 19, 2014 at 4:53 PM, Jay Patel pateljay3...@gmail.com wrote:
When coordinator fires indexed scan
Hey there,
We've trying out Cassandra-2.1.1 and facing the below exception frequently,
mainly during the node reboot. File is there with proper permissions (as
below), not sure why C* is not able to find it.
ERROR [OptionalTasks:1] 2014-09-27 16:00:20,888 CassandraDaemon.java:167 -
Exception
Hi,
We converted column families from ST to Leveled Compaction strategy, but
build-in secondary indexes are not converted to Leveled Compaction. Is
there any specific parameter we need to define for Indexes or will it
derive compaction strategy from the primary table OR, Do we need to rebuild
