[
https://issues.apache.org/jira/browse/CASSANDRA-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615602#comment-14615602
]
Ariel Weisberg commented on CASSANDRA-9683:
-------------------------------------------
How are you getting fraction of a millisecond latency operating on 300 megabyte
rows? What is the workload that latency is being measured for in read/write?
Can you provide more specific steps to reproduce? I can't tell what you are
measuring and what your configuration is nor what the simplest configuration I
can set up to see this is.
How many nodes, how many DCs?
> 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, 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)
