[
https://issues.apache.org/jira/browse/CASSANDRA-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625518#comment-14625518
]
Ariel Weisberg commented on CASSANDRA-9683:
-------------------------------------------
So 2.1.8 doesn't have the same performance issue that is addressed by nodetool
disableautocompaction that 2.1.7 has?
That it is gone is good. I will look at the diff between the three releases to
see if we can find out what change caused it. If it was compaction I would have
thought I would be able to reproduce it on one node when I upgraded from 2.1.6
to 2.1.7. When I upgraded I didn't see any compactions and there was no load
from the C* process.
> Get mucher higher load and latencies after upgrading from 2.1.6 to cassandra
> 2.1.7
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-9683
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9683
> Project: Cassandra
> Issue Type: Bug
> Environment: Ubuntu 12.04 (3.13 Kernel) * 3
> JDK: Oracle JDK 7
> RAM: 32GB
> Cores 4 (+4 HT)
> Reporter: Loic Lambiel
> Assignee: Ariel Weisberg
> Fix For: 2.1.x
>
> Attachments: cassandra-env.sh, cassandra.yaml, cfstats.txt,
> os_load.png, pending_compactions.png, read_latency.png, schema.txt,
> system.log, write_latency.png
>
>
> After upgrading our cassandra staging cluster version from 2.1.6 to 2.1.7,
> the average load grows from 0.1-0.3 to 1.8.
> Latencies did increase as well.
> We see an increase of pending compactions, probably due to CASSANDRA-9592.
> This cluster has almost no workload (staging environment)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
