Skip to content

CASSANALYTICS-112: Support integration tests after Transactional Cluster Metadata - #246

Open
michaelsembwever wants to merge 4 commits into
apache:trunkfrom
thelastpickle:mck/112/trunk
Open

michaelsembwever wants to merge 4 commits into
apache:trunkfrom
thelastpickle:mck/112/trunk

Conversation

@michaelsembwever

Copy link
Copy Markdown
Member

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.

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
@michaelsembwever michaelsembwever changed the title Support integration tests after Transactional Cluster Metadata CASSANALYTICS-112 Support integration tests after Transactional Cluster Metadata Sep 18, 2026

@bbotella bbotella left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

…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

Copy link
Copy Markdown
Member Author

@bbotella ,

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

done. plus fixes to get those tests working stable.

@yifan-c yifan-c changed the title CASSANALYTICS-112 Support integration tests after Transactional Cluster Metadata CASSANALYTICS-112: Support integration tests after Transactional Cluster Metadata Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants