[
https://issues.apache.org/jira/browse/CASSANDRA-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610794#comment-14610794
]
Ariel Weisberg commented on CASSANDRA-9683:
-------------------------------------------
[~llambiel] I would like to try and reproduce this. You say there is almost no
load. How many column families and how much data per? Is it possible to get the
schema or at least a summary? Specifically interested in what compaction
strategies are in use and what the compression configuration is as well as
replication factor and strategy as well as the write consistency level in use.
You say almost no load, so what percentage of peak capacity is the write load
that you are using to measure latency?
Is this reproducible on a single node?
> 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.yaml, os_load.png, pending_compactions.png,
> read_latency.png, 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)
