Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Quality Assurance
-
Normal
-
All
-
None
-
Description
This is a spinoff from CASSANDRA-19769 to lower the patch size
To help validate the cluster state it is good to put a cluster into random situations to make sure it still works correctly. CASSANDRA-19769 Added such a test and found several issues with TCM (all fixed) and can be used to help find more issues as we expand the scope of what it can touch.
I propose we have a test that randomizes changes to the topology, performs cluster operations such as repair, and performs CQL operations (for this patch using Harry)
Attachments
Attachments
Issue Links
- is blocked by
-
CASSANDRA-19872 Handle losing CMS status while committing a transformation
- Resolved
- relates to
-
CASSANDRA-19768 nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
- Resolved
-
CASSANDRA-19769 CEP-15: (Accord) sequence EpochReady.coordinating to allow syncComplete to be learned from newer epochs
- Resolved
-
CASSANDRA-19782 Host replacements no longer fully populate system.peers table
- Resolved
-
CASSANDRA-19761 When JVM dtest is shutting down, if a new epoch is being committed the node is unable to shut down
- Resolved
-
CASSANDRA-19705 Reconfigure CMS after move/bootstrap/replacement
- Resolved
- links to