cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12668) Memtable Contention in 2.1
Date Mon, 19 Sep 2016 23:16:20 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504996#comment-15504996
] 

Benedict commented on CASSANDRA-12668:
--------------------------------------

To respond to your edit:

bq. Is there any warning in NEWS.txt 

You're only just bringing this particular aspect of tradeoff to light now.  Tradeoffs happen
whether we know about them or not, and the fact it's taken so long to come to light suggests
it was perhaps a perfectly reasonable hidden tradeoff.

But, anyway, we can't talk about a tradeoff meaningfully until we know both sides of the trade.
 Let's leave that discussion until we actually know the cause.

If you're right about the cause, the absolute worst case scenario IMO is to provide a patch
to make the collection pluggable.

> Memtable Contention in 2.1
> --------------------------
>
>                 Key: CASSANDRA-12668
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12668
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: sankalp kohli
>
> We added a new Btree implementation in 2.1 which causes write performance to go down
in Cassandra if there is  lot of contention in the memtable for a CQL partition. Upgrading
a cluster from 2.0 to 2.1 with contention causes the cluster to fall apart due to GC. We tried
making the defaults added in CASSANDRA-7546 configurable but that did not help. Is there anyway
to fix this issue?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message