cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Bossa (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-6678) Unwanted schema pull while upgrading nodes from 1.2 to 2.0
Date Fri, 07 Feb 2014 13:34:19 GMT
Sergio Bossa created CASSANDRA-6678:
---------------------------------------

             Summary: 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


While upgrading from 1.2 to 2.0, the 1.2 nodes are not supposed to pull schemas 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 MessagingService, which is activated after
the Gossiper and handles network version 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 version upon receiving
the first gossip message of an upgraded node: thoughts?



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

Mime
View raw message