[
https://issues.apache.org/jira/browse/CASSANDRA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russ Hatch updated CASSANDRA-6943:
----------------------------------
Attachment: node7.log
node6.log
node5.log
node4.log
attaching node logs
here's the graph as well:
http://riptano.github.io/cassandra_performance/graph/graph.html?stats=6943.read_write.uber_contention_CL_one.austin.json
This is very similar to the earlier graphs, but if needed we can use the data
in the json to correlate to events in the node logs.
> very contentious writes result in performance degradation
> ---------------------------------------------------------
>
> Key: CASSANDRA-6943
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6943
> Project: Cassandra
> Issue Type: Bug
> Reporter: Russ Hatch
> Attachments: node4.log, node4_jstack.log, node5.log,
> node5_jstack.log, node6.log, node6_jstack.log, node7.log, node7_jstack.log,
> screenshot.png, screenshot2.png, stress_jstack.log
>
>
> Running performance scenarios I have seen this characteristic drop in
> performance happen several times. A similar effect was reproduced in another
> test cluster. Operations eventually come to a standstill.
> !screenshot.png!
> !screenshot2.png!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
