[ https://issues.apache.org/jira/browse/CASSANDRA-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701447#comment-14701447 ]
Ryan McGuire commented on CASSANDRA-9554: ----------------------------------------- We have some dtest code that exemplifies how to read from traces here : https://github.com/riptano/cassandra-dtest/blob/master/replication_test.py#L49-L109 We'll talk in standup today who can take this on. > 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 beta 2 > > > 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)