[ https://issues.apache.org/jira/browse/CASSANDRA-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880815#comment-13880815 ]
Cyril Scetbon commented on CASSANDRA-4880: ------------------------------------------ When I upgrade one node from 1.2.2 to 1.2.13 for 2h I get the previous messages with a raise of CPU(as it flush and compact continually) on all nodes http://picpaste.com/pics/Screen_Shot_2014-01-24_at_09.18.50-ggcCDVqd.1390551670.png After that, everything is fine and I can upgrade other nodes without any important raise of cpus load. when I start the upgrade, the more nodes I upgrade at the same time (at the beginning), the higher the cpu load is http://picpaste.com/pics/Screen_Shot_2014-01-23_at_17.45.56-I3fdEQ2T.1390552036.png > Endless loop flushing+compacting system/schema_keyspaces and > system/schema_columnfamilies > ----------------------------------------------------------------------------------------- > > Key: CASSANDRA-4880 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4880 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.1.6, 1.2.0 beta 1 > Environment: Linux x86_64 3.4.9, sun-jdk 1.6.0_33 > Reporter: Mina Naguib > Assignee: Pavel Yaskevich > Fix For: 1.1.7, 1.2.0 beta 3 > > Attachments: 131203-schema-1.txt, 131203-schema-2.txt, > CASSANDRA-4880-fix.patch, CASSANDRA-4880.patch > > > After upgrading a node from 1.1.2 to 1.1.6, the startup sequence entered a > loop as seen here: > http://mina.naguib.ca/misc/cassandra_116_startup_loop.txt > Stopping and starting the node entered the same loop. > Reverting back to 1.1.2 started successfully. -- This message was sent by Atlassian JIRA (v6.1.5#6160)