tiering
Retry one stalled tiering partition
Changed onRe-runs one supervised executor attempt for a stalled partition. The request must include nodeId and the current stateToken from /tiering/plan; stale tokens return 409. Like apply, the leg runs detached from the request and the 202 acknowledges admission with outcome "started".
post/tiering/tables/{database}/{table}/partitions/{partitionId}/retry
Request
- Base URL: /api/v1 (relative, and the document was published on a file host, not at the API’s origin)
- URL: /api/v1/tiering/tables/{database}/{table}/partitions/{partitionId}/retry
- Auth: none declared
Path parameters
databasestring required
Example:movoor_dev
ClickHouse database name.
tablestring required
Example:test_generic_network_month_local
ClickHouse table name.
partitionIdstring required
Example:d82d64de29c8683be4aad2f0fd38d74e
ClickHouse partition_id verbatim.
Query parameters
nodeIdstring required
Example:shard1-replica1
Movoor configured node id. Tiering actions are node-local.
Request body
Response
Retry admitted; the leg runs in the background.
Example response
{
"item": {
"outcome": "success",
"bytes": "104"
}
}Changes
- info
endpoint added
- info