>> Hi,
>>
>> I've begun experiencing very high tail latencies across my clusters.
>> While Cassandra's internal metrics report <1ms read latencies, measuring
>> responses from within the driver in my applications (roundtrips of
>> query/execute frames), h
that should give you per-collection breakdowns.
--Bryan
On Wed, Jul 6, 2016 at 6:22 PM, Nimi Wariboko Jr <n...@channelmeter.com>
wrote:
> Hi,
>
> I've begun experiencing very high tail latencies across my clusters. While
> Cassandra's internal metrics report <1ms read
Hi,
I've begun experiencing very high tail latencies across my clusters. While
Cassandra's internal metrics report <1ms read latencies, measuring
responses from within the driver in my applications (roundtrips of
query/execute frames), have 90% round trip times of up to a second for very
ba
thread_key = 'fastcompany:3000619';
The read latencies seem really high (upwards of 500ms)? Or is this
expected? Is this bad schema, or…? What's the best way to trace the
bottleneck, besides this tracing query:
http://pastebin.com/sherFpgY
Or, how would you interpret that?
I'm not sure that row
Hi.
I have a table with about 300k rows in it, and am doing a query that returns
about 800 results.
select * from fc.co WHERE thread_key = 'fastcompany:3000619';
The read latencies seem really high (upwards of 500ms)? Or is this expected? Is
this bad schema, or…? What's the best way to trace
