Details
-
New Feature
-
Status: Resolved
-
Normal
-
Resolution: Fixed
Description
In order to support the sidecar-managed restore jobs (sidecar counterpart of Cassandra analytics bulk write via S3), it is required to have the capability to perform consistency check for the individual restore ranges and have a new endpoint for the spark job to query the restore progress.
The consistency check should be responsive to cluster topology changes. For example, if there is a new node joining the cluster, the write replica set of the affected ranges are changed. The joining node should be able to discover the restore ranges that it owns and restore the data.
Attachments
Issue Links
- links to