[ https://issues.apache.org/jira/browse/CASSANDRA-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Strickland updated CASSANDRA-9607: ----------------------------------------- Attachment: vm_monitor.png GC_state.png dump.tdump cpu_profile.png client_blocked_thread.png I was able to bring the data down to my local machine and replicate the issue on a fresh install while profiling. I've attached screen shots of the session, as well as the thread state on the client while it's happening. You can see the server blocking on select and the client blocking on accept, which of course causes both ends to become unresponsive. > Get high load after upgrading from 2.1.3 to cassandra 2.1.6 > ----------------------------------------------------------- > > Key: CASSANDRA-9607 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9607 > Project: Cassandra > Issue Type: Bug > Environment: OS: > CentOS 6 * 4 > Ubuntu 14.04 * 2 > JDK: Oracle JDK 7, Oracle JDK 8 > VM: Azure VM Standard A3 * 6 > RAM: 7 GB > Cores: 4 > Reporter: Study Hsueh > Assignee: Tyler Hobbs > Priority: Critical > Fix For: 2.1.x, 2.2.x > > Attachments: GC_state.png, cassandra.yaml, client_blocked_thread.png, > cpu_profile.png, dump.tdump, load.png, log.zip, schema.zip, vm_monitor.png > > > After upgrading cassandra version from 2.1.3 to 2.1.6, the average load of my > cassandra cluster grows from 0.x~1.x to 3.x~6.x. > What kind of additional information should I provide for this problem? -- This message was sent by Atlassian JIRA (v6.3.4#6332)