Devesh Kumar Singh created HDDS-15165:
-----------------------------------------
Summary: Recon: Add admin REST APIs to trigger, monitor, and
cancel SCM DB snapshot sync
Key: HDDS-15165
URL: https://issues.apache.org/jira/browse/HDDS-15165
Project: Apache Ozone
Issue Type: Task
Components: Ozone Recon
Reporter: Devesh Kumar Singh
Assignee: Devesh Kumar Singh
Recon currently performs SCM container synchronization through periodic
targeted sync, with full SCM DB snapshot sync used as an expensive recovery
path when drift becomes large. Since full SCM DB snapshot download can be
resource-heavy on large clusters, operators should be able to explicitly
control this operation and observe its progress.
Add admin-only Recon REST APIs for full SCM DB snapshot sync management:
{code:java}
POST /api/v1/triggerdbsync/scm/snapshot
GET /api/v1/triggerdbsync/scm/snapshot/status
POST /api/v1/triggerdbsync/scm/snapshot/cancel
{code}
*Expected behavior:*
{code:java}
- POST /scm/snapshot starts an asynchronous full SCM DB checkpoint download
and Recon SCM DB refresh.
- GET /scm/snapshot/status returns current status, start time, duration,
phase, and last error if any.
- POST /scm/snapshot/cancel cancels the snapshot operation while it is still
in the checkpoint download/pre-swap phase.
- The API should reject duplicate trigger requests while a snapshot sync is
already running.
- The operation should clean up temporary checkpoint files on failure or
cancellation.
- Existing targeted SCM sync should continue to use the current POST
/api/v1/triggerdbsync/scm endpoint.
{code}
This can later be exposed through ozone admin recon CLI as a thin wrapper
over the REST APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
