You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2011/07/05 23:28:16 UTC
[jira] [Created] (CASSANDRA-2860) Versioning works *too* well
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: Brandon Williams
Fix For: 0.8.2
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
[jira] [Updated] (CASSANDRA-2860) Versioning works *too* well
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2860:
--------------------------------------
Attachment: 2860-v2.txt
v2 moves reset call into OTC.disconnect, so it will work even if the restart time is too small for FD to kick in
> 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: Brandon Williams
> 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
[jira] [Commented] (CASSANDRA-2860) Versioning works *too* well
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-2860) Versioning works *too* well
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2860:
--------------------------------------
Attachment: 2860.txt
patch to reset protocol-version-to-attempt when MessagingService resets a connection pool (when FD notices it's down)
> 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: Brandon Williams
> Fix For: 0.8.2
>
> Attachments: 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
[jira] [Commented] (CASSANDRA-2860) Versioning works *too* well
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065423#comment-13065423 ]
Brandon Williams commented on CASSANDRA-2860:
---------------------------------------------
+1
> 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