Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 14 Mar 2014 23:50:43 +0000 (UTC)
From: "Oleg Anastasyev (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12701546.1394822268504.74071.1394841043828@arcas>
In-Reply-To: <JIRA.12701546.1394822268504@arcas>
References: <JIRA.12701546.1394822268504@arcas>
Subject: [jira] [Issue Comment Deleted] (CASSANDRA-6862) Schema versions
 mismatch on large ring
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Anastasyev updated CASSANDRA-6862:
---------------------------------------

    Comment: was deleted

(was: LGTM. Oh those range tombstones, everybody forget about them...;-)
)

> 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.2#6252)