[ https://issues.apache.org/jira/browse/CASSANDRA-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279521#comment-15279521 ]
Michael Fong commented on CASSANDRA-6862: ----------------------------------------- Hi, We have recently seen schema version mismatch issue while doing rolling upgrade from 1.2.19 to 2.0.17. What is worse is that the mismatch could lead to a rapid and massive message exchange of schema information across nodes, and sometimes may lead to node OOM. I opened a ticket regarding this at CASSANDRA-11748 Have you observed the heap over usage on exchanging schema information before? > Schema versions mismatch on large ring > -------------------------------------- > > Key: CASSANDRA-6862 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6862 > Project: Cassandra > Issue Type: Bug > 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)