[
https://issues.apache.org/jira/browse/CASSANDRA-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878103#comment-13878103
]
Cyril Scetbon edited comment on CASSANDRA-4880 at 1/22/14 10:39 PM:
--------------------------------------------------------------------
I can easily reproduce it by having one DC with 1.2.2 and another with
1.2.12/1.2.13. see http://pastebin.com/YZKUQLXz
If I grep for only InternalResponseStage logs I get
http://pastebin.com/htnXZCiT which always displays same account of ops and
serialized/live bytes per column family. Column family system/schema_columns is
also concerned by this issue.
was (Author: cscetbon):
I can easily reproduce it by having one DC with 1.2.2 and another with 1.2.13.
see http://pastebin.com/YZKUQLXz
If I grep for only InternalResponseStage logs I get
http://pastebin.com/htnXZCiT which always displays same account of ops and
serialized/live bytes per column family. Column family system/schema_columns is
also concerned by this issue.
> 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)