[
https://issues.apache.org/jira/browse/CASSANDRA-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195242#comment-14195242
]
sankalp kohli commented on CASSANDRA-6862:
------------------------------------------
"Also, the proper fix here was probably to figure out why different nodes had
differing tombstones, and fix that, instead of excluding them from digest
altogether."
Different nodes don't have differing tombstones. The problem is that 1.2
machines are adding the tombstones in its schema version and 2.0 are not. This
will cause schema to never agree even with same tombstones in the ring.
This is different from schema changes due to 1.2 to 2.0 upgrade which settles
once it is propagated in the ring.
Am I missing something?
> 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)
