[
https://issues.apache.org/jira/browse/CASSANDRA-12228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405953#comment-15405953
]
Sylvain Lebresne commented on CASSANDRA-12228:
----------------------------------------------
We even wrote stuff up:
http://wiki.apache.org/cassandra/CompatibilityGuarantees, which while
absolutely imperfect is better than nothing. In particular:
bq. No removal/modifications of any configuration option, startup option,
exposed metrics or general behavior of the Cassandra process
> Write performance regression in 3.x vs 3.0
> ------------------------------------------
>
> Key: CASSANDRA-12228
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12228
> Project: Cassandra
> Issue Type: Bug
> Reporter: T Jake Luciani
> Assignee: Ariel Weisberg
> Priority: Minor
> Fix For: 3.9
>
>
> I've been tracking down a performance issue in trunk vs cassandra-3.0 branch.
> I think I've found it. CASSANDRA-6696 changed the default memtable flush
> default to 1 vs the min of 2 in cassandra-3.0.
> I don't see any technical reason for this and we should add back the min of 2
> sstable flushers per disk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
