[jira] [Updated] (CASSANDRA-9554) Avoid digest mismatch storm on upgade to 3.0

2015-08-13 Thread Jonathan Ellis (JIRA) 

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

Jonathan Ellis updated CASSANDRA-9554:
--
Assignee: Stefania  (was: Sylvain Lebresne)

 Avoid digest mismatch storm on upgade to 3.0
 

 Key: CASSANDRA-9554
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9554
 Project: Cassandra
  Issue Type: Bug
Reporter: Aleksey Yeschenko
Assignee: Stefania
 Fix For: 3.0.0 rc1


 CASSANDRA-8099, in {{UnfilteredRowIterators.digest()}}:
 {code}
 // TODO: we're not computing digest the same way that old nodes. This
 // means we'll have digest mismatches during upgrade. We should pass 
 the messaging version of
 // the node this is for (which might mean computing the digest last, 
 and won't work
 // for schema (where we announce the version through gossip to 
 everyone))
 {code}
 In a mixed 2.1(2.2) - 3.0 clusters, we need to calculate both digest at the 
 same time and keep both results, and send the appropriate one, depending on 
 receiving nodes' messaging versions. Do that until 
 {{MessagingService.allNodesAtLeast30()}} is true (this is not unprecedented).



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

[jira] [Updated] (CASSANDRA-9554) Avoid digest mismatch storm on upgade to 3.0

2015-08-13 Thread Jonathan Ellis (JIRA) 

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

Jonathan Ellis updated CASSANDRA-9554:
--
Assignee: Ariel Weisberg  (was: Stefania)

 Avoid digest mismatch storm on upgade to 3.0
 

 Key: CASSANDRA-9554
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9554
 Project: Cassandra
  Issue Type: Bug
Reporter: Aleksey Yeschenko
Assignee: Ariel Weisberg
 Fix For: 3.0.0 rc1


 CASSANDRA-8099, in {{UnfilteredRowIterators.digest()}}:
 {code}
 // TODO: we're not computing digest the same way that old nodes. This
 // means we'll have digest mismatches during upgrade. We should pass 
 the messaging version of
 // the node this is for (which might mean computing the digest last, 
 and won't work
 // for schema (where we announce the version through gossip to 
 everyone))
 {code}
 In a mixed 2.1(2.2) - 3.0 clusters, we need to calculate both digest at the 
 same time and keep both results, and send the appropriate one, depending on 
 receiving nodes' messaging versions. Do that until 
 {{MessagingService.allNodesAtLeast30()}} is true (this is not unprecedented).



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

[jira] [Updated] (CASSANDRA-9554) Avoid digest mismatch storm on upgade to 3.0

2015-08-07 Thread Tyler Hobbs (JIRA) 

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

Tyler Hobbs updated CASSANDRA-9554:
---
Assignee: Sylvain Lebresne  (was: Tyler Hobbs)

Reassigning to Sylvain for now.

 Avoid digest mismatch storm on upgade to 3.0
 

 Key: CASSANDRA-9554
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9554
 Project: Cassandra
  Issue Type: Bug
Reporter: Aleksey Yeschenko
Assignee: Sylvain Lebresne
 Fix For: 3.0.0 rc1


 CASSANDRA-8099, in {{UnfilteredRowIterators.digest()}}:
 {code}
 // TODO: we're not computing digest the same way that old nodes. This
 // means we'll have digest mismatches during upgrade. We should pass 
 the messaging version of
 // the node this is for (which might mean computing the digest last, 
 and won't work
 // for schema (where we announce the version through gossip to 
 everyone))
 {code}
 In a mixed 2.1(2.2) - 3.0 clusters, we need to calculate both digest at the 
 same time and keep both results, and send the appropriate one, depending on 
 receiving nodes' messaging versions. Do that until 
 {{MessagingService.allNodesAtLeast30()}} is true (this is not unprecedented).



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

[jira] [Updated] (CASSANDRA-9554) Avoid digest mismatch storm on upgade to 3.0

2015-06-28 Thread Jonathan Ellis (JIRA) 

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

Jonathan Ellis updated CASSANDRA-9554:
--
Fix Version/s: (was: 3.0 beta 1)
   3.0.0 rc1

 Avoid digest mismatch storm on upgade to 3.0
 

 Key: CASSANDRA-9554
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9554
 Project: Cassandra
  Issue Type: Bug
Reporter: Aleksey Yeschenko
Assignee: Tyler Hobbs
 Fix For: 3.0.0 rc1


 CASSANDRA-8099, in {{UnfilteredRowIterators.digest()}}:
 {code}
 // TODO: we're not computing digest the same way that old nodes. This
 // means we'll have digest mismatches during upgrade. We should pass 
 the messaging version of
 // the node this is for (which might mean computing the digest last, 
 and won't work
 // for schema (where we announce the version through gossip to 
 everyone))
 {code}
 In a mixed 2.1(2.2) - 3.0 clusters, we need to calculate both digest at the 
 same time and keep both results, and send the appropriate one, depending on 
 receiving nodes' messaging versions. Do that until 
 {{MessagingService.allNodesAtLeast30()}} is true (this is not unprecedented).



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