tiering

Get tiering controller status

Changed on

Returns runtime dispatch state, rate limits, and in-flight tiering legs.

get/tiering/status

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/status
  • Auth: none declared

Response

Current tiering runtime status.

mode'off' | 'plan' | 'enforce' required

Tiering execution mode.

pauseState'running' | 'stopping' | 'stopped' required

Runtime dispatch state.

pauseReasonstring
maxConcurrentPartitionsinteger required

Concurrent leg cap per node (nodes own independent disks and do not starve each other); maxBytesInFlight is the aggregate ceiling.

maxMovesPerCycleinteger required
maxBytesInFlightstring required

Exact unsigned 64-bit ClickHouse integer encoded as decimal text.

bytesInFlightstring required

Exact unsigned 64-bit ClickHouse integer encoded as decimal text.

maxBytesPerDaystring required

Exact unsigned 64-bit ClickHouse integer encoded as decimal text.

bytesMovedTodaystring required

Exact unsigned 64-bit ClickHouse integer encoded as decimal text.

updatedAtstring date-time required

Example response

{
  "inFlight": [
    {
      "bytes": "104"
    }
  ],
  "maxBytesInFlight": "104",
  "bytesInFlight": "104",
  "maxBytesPerDay": "104",
  "bytesMovedToday": "104"
}

Changes