[
https://issues.apache.org/jira/browse/CASSSIDECAR-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSSIDECAR-258:
----------------------------------
Authors: Yifan Cai
Test and Documentation Plan: ci; unit
Status: Patch Available (was: Open)
PR: [https://github.com/apache/cassandra-sidecar/pull/224]
CI:
[https://app.circleci.com/pipelines/github/yifan-c/cassandra-sidecar?branch=CASSANDRASC-258%2Ftrunk-allow-staging-when-in-import-ready-already]
> Stage restore slices when in import phase already
> -------------------------------------------------
>
> Key: CASSSIDECAR-258
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-258
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Bulk Analytics
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {color:#000000}In the coordinated write feature, when job consistency level
> is LOCAL_QUORUM or QUORUM, there is a chance that the slices are not staged
> in some nodes. Sidecar, then, errors out when processing such slice. The
> proposed solution is to allow staging such slices even if the restore job is
> in import phase already. The rationale is that when a restore job is marked
> as IMPORT_READY, the spark job has concluded that the staged slices in the
> current cluster already satisfy the consistency level. Staging and importing
> the additional slices are only going to improve the data consistency.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
