[
https://issues.apache.org/jira/browse/CASSANDRA-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193125#comment-14193125
]
Aleksey Yeschenko commented on CASSANDRA-6862:
----------------------------------------------
I'm not saying it's not a problem - just that this particular issue is
irrelevant here. Because as soon as 1.2 node upgrades to 2.0 and starts up,
we'll make change to its schema (conversion of aliases to proper columns) and
schema versions will change anyway, tombstones or not.
> Schema versions mismatch on large ring
> --------------------------------------
>
> Key: CASSANDRA-6862
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6862
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: 2.0
> Reporter: Oleg Anastasyev
> Assignee: Oleg Anastasyev
> Fix For: 2.0.7
>
> Attachments: 6862-v2.txt, SchemaVersionLiveColumns.txt
>
>
> We have a large cluster with several hundreds nodes in 1 ring. Sometimes,
> especially after massive restarts, schema versions reported on different
> nodes mismatch.
> Investigated and found, that difference is not in schema itsself, but in
> thombstones (different nodes have different set of thombstones applied to
> system tables).
> Fixed by digesting schema with thombstones removed first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
