[CASSANDRA-16759] Avoid memoizing the wrong min cluster version during upgrades - ASF JIRA

Agile Board

Attach files

Attach Screenshot

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Move

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Normal
Resolution: Fixed
Fix Version/s: 4.0-rc2, 4.0, 4.0.1
Component/s: Consistency/Coordination
Labels:
None

Bug Category:
Degradation - Other Exception
Severity:
Critical
Complexity:
Challenging
Discovered By:
DTest
Platform:

All
Impacts:

None
Since Version:

4.0-rc1
Source Control Link:

https://github.com/apache/cassandra/commit/2fba5c80ce7bf71d04c62043ffa1088b9e832d83
Test and Documentation Plan:

Hide

cci run

Show
cci run

Description

~~CASSANDRA-16525~~ avoids trying to calculate the cluster min version if gossiper is not enabled.

This makes us memoize the wrong version for up to a minute causing us to send 4.0-messages to 3.0 nodes, for example in ColumnFilter

This was discovered by python upgrade dtests, here after reverting ~~CASSANDRA-15899~~ in ~~CASSANDRA-16735~~

Attachments

Activity

Comment

This comment will be Viewable by All Users Viewable by All Users

Cancel

People

Assignee:: Marcus Eriksson Assign to me

Reporter:: Marcus Eriksson

Authors:: Jon Meredith, Marcus Eriksson

Reviewers:: Brandon Williams, Yifan Cai

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 23/Jun/21 15:19

Updated:: 01/Aug/21 11:33

Resolved:: 27/Jun/21 05:17

Agile

View on Board

Avoid memoizing the wrong min cluster version during upgrades

Details

Description

Attachments

Attachments

Activity

People

Dates

Agile

Slack

Issue deployment