[jira] [Updated] (CASSANDRA-8768) Using a Cassandra 2.0 seed doesn't allow a new Cassandra 2.1 node to bootstrap

2015-02-26 Thread Alan Boudreault (JIRA) 

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

Alan Boudreault updated CASSANDRA-8768:
---
Tester: Alan Boudreault

 Using a Cassandra 2.0 seed doesn't allow a new Cassandra 2.1 node to bootstrap
 --

 Key: CASSANDRA-8768
 URL: https://issues.apache.org/jira/browse/CASSANDRA-8768
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Ron Kuris
Assignee: Brandon Williams
Priority: Minor
 Fix For: 2.1.4

 Attachments: gossip-with-2.0-patch.txt


 If you spin up a Cassandra 2.0 cluster with some seeds, and then attempt to 
 attach a Cassandra 2.1 node to it, you get the following message:
 {code}OutboundTcpConnection.java:429 - Handshaking version with 
 /10.24.0.10{code}
 Turning on debug, you get a few additional messages:
 {code}DEBUG [WRITE-/(ip)] MessagingService.java:789 - Setting version 7 for 
 /10.24.0.10
 DEBUG [WRITE-/(ip)] OutboundTcpConnection.java:369 - Target max version is 7; 
 will reconnect with that version{code}
 However, the code never reconnects. See the comments as to why.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-8768) Using a Cassandra 2.0 seed doesn't allow a new Cassandra 2.1 node to bootstrap

2015-02-10 Thread Aleksey Yeschenko (JIRA) 

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

Aleksey Yeschenko updated CASSANDRA-8768:
-
Priority: Minor  (was: Major)

 Using a Cassandra 2.0 seed doesn't allow a new Cassandra 2.1 node to bootstrap
 --

 Key: CASSANDRA-8768
 URL: https://issues.apache.org/jira/browse/CASSANDRA-8768
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Ron Kuris
Assignee: Brandon Williams
Priority: Minor
 Fix For: 2.1.3

 Attachments: gossip-with-2.0-patch.txt


 If you spin up a Cassandra 2.0 cluster with some seeds, and then attempt to 
 attach a Cassandra 2.1 node to it, you get the following message:
 {code}OutboundTcpConnection.java:429 - Handshaking version with 
 /10.24.0.10{code}
 Turning on debug, you get a few additional messages:
 {code}DEBUG [WRITE-/(ip)] MessagingService.java:789 - Setting version 7 for 
 /10.24.0.10
 DEBUG [WRITE-/(ip)] OutboundTcpConnection.java:369 - Target max version is 7; 
 will reconnect with that version{code}
 However, the code never reconnects. See the comments as to why.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-8768) Using a Cassandra 2.0 seed doesn't allow a new Cassandra 2.1 node to bootstrap

2015-02-09 Thread Ron Kuris (JIRA) 

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

Ron Kuris updated CASSANDRA-8768:
-
Attachment: gossip-with-2.0-patch.txt

 Using a Cassandra 2.0 seed doesn't allow a new Cassandra 2.1 node to bootstrap
 --

 Key: CASSANDRA-8768
 URL: https://issues.apache.org/jira/browse/CASSANDRA-8768
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Ron Kuris
 Attachments: gossip-with-2.0-patch.txt


 If you spin up a Cassandra 2.0 cluster with some seeds, and then attempt to 
 attach a Cassandra 2.1 node to it, you get the following message:
 {code}OutboundTcpConnection.java:429 - Handshaking version with 
 /10.24.0.10{code}
 Turning on debug, you get a few additional messages:
 {code}DEBUG [WRITE-/(ip)] MessagingService.java:789 - Setting version 7 for 
 /10.24.0.10
 DEBUG [WRITE-/(ip)] OutboundTcpConnection.java:369 - Target max version is 7; 
 will reconnect with that version{code}
 However, the code never reconnects. See the comments as to why.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)