Re: timeouts on counter tables

[Rudi Bruchez]

I'm going to try different options. Do any of you have some experience with tweaking one of those conf parameters to improve read throughput, especially in case of counter tables ?

1/ using SSD :
trickle_fsync: true
trickle_fsync_interval_in_kb: 1024

2/ concurrent_compactors to the number of cores.

3/ concurrent_counter_writes

4/ Row Cache vs Chunk Cache



thanks !

5/ change the compaction method to leveled, specifically when using counter columns ??

On 3 September 2017 at 20:25, Rudi Bruchez <r...@babaluga.com <mailto:r...@babaluga.com>> wrote:

    Le 30/08/2017 à 05:33, Erick Ramirez a écrit :

    Is it possible at all that you may have a data hotspot if it's
    not hardware-related?

    It does not seem so, The partition key seems well distributed and
    the queries update different keys.

    We have dropped counter_mutation messages in the log :

    COUNTER_MUTATION messages were dropped in last 5000 ms: 0
    internal and 2 cross node. Mean internal dropped latency: 0 ms
    and Mean cross-node dropped latency: 5960 ms


    ReadStage    32 503        7481787         0                 0


    The load could be too high ?

    Thanks

Pool Name Active Pending Completed Blocked All Time Blocked CounterMutationStage 32 221 5722101 0 0

<<attachment: rudi.vcf>>

smime.p7s
Description: Signature cryptographique S/MIME