Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 7 Feb 2014 15:52:19 +0000 (UTC)
From: =?utf-8?Q?Piotr_Ko=C5=82aczkowski_=28JIRA=29?= <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12693890.1391779998097.5133.1391788339956@arcas>
In-Reply-To: <JIRA.12693890.1391779998097@arcas>
References: <JIRA.12693890.1391779998097@arcas>
Subject: [jira] [Commented] (CASSANDRA-6678) Unwanted schema pull while
 upgrading nodes from 1.2 to 2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-6678?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13894649#comment-13894649 ]=20

Piotr Ko=C5=82aczkowski commented on CASSANDRA-6678:
-----------------------------------------------

For upgrade to work, do I need to patch 1.2? Or is it enough to patch 2.0?

> Unwanted schema pull while upgrading nodes from 1.2 to 2.0
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-6678
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6678
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Sergio Bossa
>            Assignee: Sergio Bossa
>             Fix For: 1.2.16, 2.0.6
>
>         Attachments: CASSANDRA-6678-1_2.patch, CASSANDRA-6678-2_0.patch
>
>
> While upgrading from 1.2 to 2.0, the 1.2 nodes are not supposed to pull s=
chemas from upgraded 2.0 nodes to avoid conflicts.
> This relies on network version checks between the two nodes, but there's =
a bit of a race between the Gossiper, which is activated first, and the Mes=
sagingService, which is activated after the Gossiper and handles network ve=
rsion exchange: if a 1.2 node Gossiper gets a gossip message from a newly 2=
.0 node *before* opening connections from the MessagingService, the version=
 will still be 1.2, and the schema will be pulled from the new node.
> A possible solution may be to have the Gossiper update the network versio=
n upon receiving the first gossip message of an upgraded node: thoughts?


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)