[
https://issues.apache.org/jira/browse/CASSANDRA-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631513#comment-14631513
]
Ariel Weisberg commented on CASSANDRA-9683:
-------------------------------------------
OK, so that might explain it. The metric you are looking at for writes might
not include replication. These are screenshots from OpsCenter? I will look into
how those metrics are collected.
Durable writes don't impact replication much since it still has to occur. All
durable writes does disable writing to the commit log at each node.
I will try again with multiple nodes and keep an eye on the ops center metrics.
> 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)
