[ https://issues.apache.org/jira/browse/CASSANDRA-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David King updated CASSANDRA-2058: ---------------------------------- Attachment: graph b.png graph a.png Just had this happen again, attaching load/CPU graphs. Will have logs shortly. I was in the middle of pushing out the change to turn off the DES. This is pmc14. As of when this happened, the nodes {pmc01 pmc04 pmc07 pmc10 pmc13 pmc16} had it turned off but the others have not been restarted > Nodes periodically spike in load > -------------------------------- > > Key: CASSANDRA-2058 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2058 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 0.6.10 > Reporter: David King > Attachments: cassandra.pmc01.log.bz2, graph a.png, graph b.png > > > (Filing as a placeholder bug as I gather information.) > At ~10p 24 Jan, I upgraded our 20-node cluster from 0.6.8->0.6.10, turned on > the DES, and moved some CFs from one KS into another (drain whole cluster, > take it down, move files, change schema, put it back up). Since then, I've > had four storms whereby a node's load will shoot to 700+ (400% CPU on a 4-cpu > machine) and become totally unresponsive. After a moment or two like that, > its neighbour dies too, and the failure cascades around the ring. > Unfortunately because of the high load I'm not able to get into the machine > to pull a thread dump to see wtf it's doing as it happens. > I've also had an issue where a single node spikes up to high load, but > recovers. This may or may not be the same issue from which the nodes don't > recover as above, but both are new behaviour -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.