You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "sankalp kohli (JIRA)" <ji...@apache.org> on 2016/09/19 19:49:21 UTC

[jira] [Comment Edited] (CASSANDRA-12668) Memtable Contention in 2.1

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

sankalp kohli edited comment on CASSANDRA-12668 at 9/19/16 7:49 PM:
--------------------------------------------------------------------

The cluster was doing constant Java GC and was not able to stay up. Is there anything else you are looking for?


was (Author: kohlisankalp):
The cluster was doing constant Java GC and was not able to stay up. 

> 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)