CASSSIDECAR-373: Define storage provider interface and Cassandra implementation to support durable job tracking#339
Open
andresbeckruiz wants to merge 10 commits into
Open
Conversation
isaacreath
suggested changes
Apr 24, 2026
isaacreath
reviewed
Apr 30, 2026
| { | ||
| BoundStatement statement = tableSchema.trySetActive().bind(clusterName, operationType, operationId); | ||
| statement.setConsistencyLevel(ConsistencyLevel.LOCAL_QUORUM); | ||
| statement.setSerialConsistencyLevel(ConsistencyLevel.LOCAL_SERIAL); |
Contributor
There was a problem hiding this comment.
Shouldn't we be using global SERIAL to ensure the active operation will be consistent across all DCs?
Contributor
Author
There was a problem hiding this comment.
We are initially defaulting to LOCAL_SERIAL because GLOBAL_SERIAL for globally distributed clusters (eg: us-east, us-west, eu) would likely timeout. LOCAL_SERIAL can still guarantee that we only have one job ongoing per datacenter, assuming submitted nodes are restricted to that DC.
Once configuration is added for the operational job framework, we should allow consistency level to be set as needed.
Contributor
There was a problem hiding this comment.
If we're going for per-DC jobs, then it may make sense to add this into the schema as well so that we can get the active job by DC.
Contributor
Author
There was a problem hiding this comment.
Added datacenter to ActiveClusterOps schema in 55bdd43
andresbeckruiz
force-pushed
the
CASSSIDECAR-373
branch
3 times, most recently
from
6c99923 to
e5a64df
Compare
pauloricardomg
approved these changes
May 19, 2026
…ementation to support durable job tracking
andresbeckruiz
force-pushed
the
CASSSIDECAR-373
branch
from
55bdd43 to
aa61a52
Compare
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
3 participants
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.
CASSSIDECAR-373
Implements
CassandraStorageProvider, the default Cassandra backed implementation of theStorageProviderinterface for durable operational job state.Changes
StorageProviderinterface, which adds a provider-agnostic abstraction for persisting, querying, and coordinating operational jobsOperationalJobRecordis the data transfer object representing persisted job stateOperationalJobConfigurationprovides configurable table TTL, and in the future can support remote Cassandra cluster connectionThree Cassandra table schemas:
cluster_ops— persists and tracks operational jobs (restarts, upgrades, etc.)cluster_ops_node_state— tracks per-node status within an operationactive_cluster_ops— provides mutual exclusion of concurrent operations via LWTDatabase accessors: (
ClusterOpsDatabaseAccessor,ClusterOpsNodeStateDatabaseAccessor,ActiveClusterOpsDatabaseAccessor)CassandraStorageProvidercomposes the three accessors, acts as thin delegation layerIntegration tests for all three database accessors
Future Work