[jira] [Updated] (CASSANDRA-12676) Message coalescing regression

["Jeff Jirsa (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-12676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Jirsa updated CASSANDRA-12676:
-----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 3.11.x)
                   3.11.0
                   3.0.12
           Status: Resolved  (was: Patch Available)

Committed in {{e11f75081727e650353ac12ec50f508fa9387d60}} and merged up through trunk.

I've only changed NEWS.txt on 3.0:

{quote}
+   - In 2.1, the default for otc_coalescing_strategy was 'DISABLED'.
 +     In 2.2 and 3.0, it was changed to 'TIMEHORIZON', but that value was shown
 +     to be a performance regression. The default for 3.11.0 and newer has
 +     been reverted to 'DISABLED'. Users upgrading to Cassandra 3.0 should
 +     consider setting otc_coalescing_strategy to 'DISABLED'.
{quote}

And used a slightly different wording on 3.11 and trunk (in addition to actually changing the default:

{quote}
+   - In 2.1, the default for otc_coalescing_strategy was 'DISABLED'.
 +     In 2.2 and 3.0, it was changed to 'TIMEHORIZON', but that value was shown
 +     to be a performance regression. The default for 3.11.0 and newer has
 +     been reverted to 'DISABLED'. Users upgrading from Cassandra 2.2 or 3.0 should
 +     be aware that the default has changed.
{quote}


> Message coalescing regression
> -----------------------------
>
>                 Key: CASSANDRA-12676
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12676
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Assignee: Jeff Jirsa
>              Labels: docs-impacting
>             Fix For: 3.0.12, 3.11.0, 4.0
>
>         Attachments: 12676.diff, coalescing_disabled.png, result.html
>
>
> 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
(v6.3.15#6346)