Repository navigation
CASSANALYTICS-112: Support integration tests after Transactional Cluster Metadata - #246
Open
michaelsembwever wants to merge 4 commits into
Open
michaelsembwever wants to merge 4 commits into
michaelsembwever wants to merge 4 commits into
Conversation
Select topology-change hooks for legacy Cassandra and Transactional Cluster Metadata. Create schema before supported transitions and configure three metadata replicas on Cassandra 6.0 and later. Retain single-node success and failure scenarios, including multi-datacenter coverage, across supported versions. Preserve concurrent joins and leaves and cluster-doubling/halving scenarios for Cassandra older than 6.0, with their required range-movement settings scoped to those tests and restored during teardown. Exercise concurrent TCM joins and leaves with Sidecar's CASSSIDECAR-277 disjoint token placement, including a join in an unreplicated datacenter. Preserve the existing consistency-level and per-node data checks. Wait for joining and replacement startup before shutdown, require successful joins to reach Normal, and await decommission results before validating writes. Inject terminal leave failures and verify the expected error. Add completion regression tests and raise the integration JVM datagram-socket limit for multi-node tests. patch by Mick Semb Wever for CASSANALYTICS-112 Assisted-by: Codex:GPT-6
bbotella
reviewed
Sep 23, 2026
bbotella
left a comment
Contributor
There was a problem hiding this comment.
Quick (probably dumb) question. Should we have Cassandra 6.0 entries here?
https://github.com/apache/cassandra-analytics/blob/trunk/.github/workflows/test.yaml#L247
…atrix (for spark 3 and 4)
michaelsembwever
force-pushed
the
mck/112/trunk
branch
from
October 4, 2026 13:32
eef1f21 to
c72fca8
Compare
…er construction Support integration tests after Transactional Cluster Metadata Transactional Cluster Metadata (TCM) changes the hooks and sequencing needed to test writes during topology changes. Create schema before transitions and configure three metadata replicas before stopping or removing nodes on Cassandra 6.0. Await transition completion so data checks cannot pass while a join, replacement, or decommission is still running. Keep concurrent transitions that require overlapping range locks on legacy Cassandra. Exercise concurrent TCM joins and leaves with Sidecar's CASSSIDECAR-277 disjoint token placement, including a join in an unreplicated datacenter. Retain consistency-level and per-node data checks, and scope legacy range-movement overrides to the tests that require them. Run Cassandra 6.0-alpha2 integration tests with Spark 3 and Spark 4, building the dtest dependency for each Java version. Increase the integration JVM datagram-socket limit to accommodate multi-node clusters. Offline Cassandra 6.0 schema commits do not notify the listener that creates keyspace instances. SSTable writer construction can therefore replace the schema while another task builds or reads a table. Preserve existing instances across those commits and use the same lock for writer construction, schema building, and scanner table lookup. This prevents missing-keyspace failures from masking the consistency and corruption failures under test. patch by Mick Semb Wever for CASSANALYTICS-112 Assisted-by: Codex:GPT-6
michaelsembwever
force-pushed
the
mck/112/trunk
branch
from
October 5, 2026 10:22
2633711 to
f673705
Compare
Member
Author
done. plus fixes to get those tests working stable. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Select topology-change hooks for legacy Cassandra and Transactional Cluster Metadata. Create schema before supported transitions and configure three metadata replicas on Cassandra 6.0 and later.
Retain single-node success and failure scenarios, including multi-datacenter coverage, across supported versions. Preserve concurrent joins and leaves and cluster-doubling/halving scenarios for Cassandra older than 6.0, with their required range-movement settings scoped to those tests and restored during teardown.
Exercise concurrent TCM joins and leaves with Sidecar's CASSSIDECAR-277 disjoint token placement, including a join in an unreplicated datacenter. Preserve the existing consistency-level and per-node data checks.
Wait for joining and replacement startup before shutdown, require successful joins to reach Normal, and await decommission results before validating writes. Inject terminal leave failures and verify the expected error. Add completion regression tests and raise the integration JVM datagram-socket limit for multi-node tests.