cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2860) Versioning works *too* well
Date Sat, 16 Jul 2011 02:16:00 GMT

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

Hudson commented on CASSANDRA-2860:
-----------------------------------

Integrated in Cassandra-0.8 #218 (See [https://builds.apache.org/job/Cassandra-0.8/218/])
    reset protocol-version-to-attempt when reconnecting to a node
patch by jbellis; reviewed by brandonwilliams for CASSANDRA-2860

jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1147355
Files : 
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/net/OutboundTcpConnection.java
* /cassandra/branches/cassandra-0.8/CHANGES.txt
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/gms/Gossiper.java


> Versioning works *too* well
> ---------------------------
>
>                 Key: CASSANDRA-2860
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2860
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.1
>            Reporter: Brandon Williams
>            Assignee: Jonathan Ellis
>             Fix For: 0.8.2
>
>         Attachments: 2860-v2.txt, 2860.txt
>
>
> The scenario goes something like this: you upgrade from 0.7 to 0.8, but all the nodes
remember that the remote side is 0.7, so they in turn speak 0.7, causing the local node to
also think the remote is 0.7, even though both are really 0.8.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message