[
https://issues.apache.org/jira/browse/CASSSIDECAR-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18083951#comment-18083951
]
Mansi Khara commented on CASSSIDECAR-454:
-----------------------------------------
CircleCI link-
https://app.circleci.com/pipelines/github/mansikhara/cassandra-sidecar?branch=CASSSIDECAR-454
> Sidecar should wake up immediately on the instance receiving a phase signal
> instead of waiting for the discovery loop
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CASSSIDECAR-454
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-454
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Bulk Analytics
> Reporter: Mansi Khara
> Assignee: Mansi Khara
> Priority: Normal
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> UpdateRestoreJobHandler writes phase signals (STAGE_READY, IMPORT_READY) to
> the DB and returns 200 with no further action, leaving the receiving instance
> idle until its next discovery cycle (up to 5–10 minutes). For IMPORT_READY,
> inject RestoreJobManagerGroup into UpdateRestoreJobHandler and call the
> existing updateRestoreJob() immediately after the DB write — staged ranges
> will unblock on the next RestoreProcessor tick (~1 second). For STAGE_READY,
> expose a package-level processJobNow(RestoreJob) method on
> RestoreJobDiscoverer that runs the same updateRestoreJob +
> processSidecarManagedJobMaybe sequence the discovery loop already executes,
> and call it from UpdateRestoreJobHandler after the DB write. Both calls are
> additive and safe to miss- the DB write remains the durable source of truth.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
