[
https://issues.apache.org/jira/browse/CASSANDRA-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192312#comment-14192312
]
Aleksey Yeschenko edited comment on CASSANDRA-6862 at 10/31/14 7:35 PM:
------------------------------------------------------------------------
bq. This will cause problems for 1.2 to 2.0 upgrade as 1.2 will add tombstones
and 2.0 won't.
Which is completely irrelevant, because of the startup migration of
CASSANDRA-5125 (see SystemKeyspace#copyAllAliasesToColumnsProper())
3.0 to 3.1 upgrade will be the first to get rid of the issue entirely, making
schema pulls, pushes, and digests fully flawless (CASSANDRA-6038).
was (Author: iamaleksey):
bq. This will cause problems for 1.2 to 2.0 upgrade as 1.2 will add tombstones
and 2.0 won't.
Which is completely irrelevant, because of the startup migration of
CASSANDRA-5125 (see SystemKeyspace#copyAllAliasesToColumnsProper())
3.0 to 3.1 upgrade will be the first to get rid of the issue entirely, making
schema pulls, pushes, and digests fully flawless.
> 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)
