cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Fong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8165) Do not include tombstones in schema version computation
Date Wed, 11 May 2016 04:12:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279499#comment-15279499
] 

Michael Fong commented on CASSANDRA-8165:
-----------------------------------------

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 https://issues.apache.org/jira/browse/CASSANDRA-11748


> Do not include tombstones in schema version computation
> -------------------------------------------------------
>
>                 Key: CASSANDRA-8165
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8165
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Vishy Kasar
>
> During 1.2.19 migration, we found the schema version mismatch issue. On digging further,
Sankalp found this was due to inclusion of the tombstones by 1.2.19 due to increased gc_grace_seconds.

> It seems wrong to include ephemeral data like tombstones in MD5 computation. Can this
be avoided?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message