[ https://issues.apache.org/jira/browse/CASSANDRA-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591977#comment-14591977 ]
Robbie Strickland commented on CASSANDRA-9607: ---------------------------------------------- Yes it does. It seems from our observation to be related to 1) our heavy use of DTCS combined with [CASSANDRA-9549|https://issues.apache.org/jira/browse/CASSANDRA-9549] and 2) severe GC pauses (such that it was GCing constantly). We were able to make things stable by moving to G1 with the following modifications: {{code}} #JVM_OPTS="$JVM_OPTS -Xmn${HEAP_NEWSIZE}" JVM_OPTS="$JVM_OPTS -XX:+UseG1GC" JVM_OPTS="$JVM_OPTS -XX:MaxGCPauseMillis=1000" JVM_OPTS="$JVM_OPTS -XX:+UseTLAB -XX:+ResizeTLAB" JVM_OPTS="$JVM_OPTS -XX:-UseBiasedLocking" {{code}} This is still a work in progress, but it has allowed us to reach a stable state. > Get high load after upgrading from 2.1.3 to cassandra 2.1.6 > ----------------------------------------------------------- > > Key: CASSANDRA-9607 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9607 > Project: Cassandra > Issue Type: Bug > Environment: OS: > CentOS 6 * 4 > Ubuntu 14.04 * 2 > JDK: Oracle JDK 7 > Reporter: Study Hsueh > Priority: Critical > Attachments: load.png > > > After upgrading cassandra version from 2.1.3 to 2.1.6, the average load of my > cassandra cluster grows from 0.x~1.x to 3.x~6.x. > What kind of additional information should I provide for this problem? -- This message was sent by Atlassian JIRA (v6.3.4#6332)