T Jake Luciani commented on CASSANDRA-12676:

If you wish to disable this on your cluster add:

otc_coalescing_strategy: DISABLED

To cassandra.yaml

> Message coalescing regression
> -----------------------------
>                 Key: CASSANDRA-12676
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12676
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>             Fix For: 2.2.x, 3.0.x
> The default in 2.2+ was to enable TIMEHORIZON message coalescing.  After 
> reports of performance regressions after upgrading from 2.1 to 2.2/3.0 we 
> have discovered the issue to be this default.
> We need to re-test our assumptions on this feature but in the meantime we 
> should default back to disabled.
> Here is a performance run [with and without message 
> coalescing|http://cstar.datastax.com/graph?command=one_job&stats=9a26b5f2-7f48-11e6-92e7-0256e416528f&metric=op_rate&operation=2_user&smoothing=1&show_aggregates=true&xmin=0&xmax=508.86&ymin=0&ymax=91223]

This message was sent by Atlassian JIRA

Reply via email to