Skip to content
ClickHouse Docs
ClickHouse DocsClickHouse Docs

Update CDC ClickPipes scaling

PATCH/v1/organizations/{organizationId}/services/{serviceId}/clickpipesCdcScaling

Update scaling settings for database ClickPipes (PostgreSQL, MySQL, MongoDB, BigQuery).

The infrastructure is shared between all database ClickPipes in the service, both for initial load and CDC. Scaling settings may take a few minutes to fully propagate.

For billing purposes, 2 CPU cores and 8 GB of RAM correspond to one compute unit. If your organization tier changes, database ClickPipes will be rescaled appropriately.

Note: For Kafka, Kinesis, and object storage pipes (S3, GCS, Azure Blob), see Get ClickPipe.

This endpoint becomes available once at least one database ClickPipe was provisioned.

Authorizations

Path parameters

  • organizationIdstringrequired

    ID of the organization that owns the service.

    format: uuid
  • serviceIdstringrequired

    ID of the service that owns the ClickPipe.

    format: uuid

Request bodyJSON

  • replicaCpuMillicoresoptionalinteger

    CPU in millicores for DB ClickPipes.

    maximum: 32000, minimum: 1000
    Example: 2000
  • replicaMemoryGboptionalnumber

    Memory in GiB for DB ClickPipes. Must be 4× the CPU core count.

    maximum: 128, minimum: 4
    Example: 8

Response

JSON

200

Successful response

JSON
  • statusoptionalnumber

    HTTP status code.

    Example: 200
  • requestIdoptionalstring

    Unique id assigned to every request. UUIDv4

    format: uuid
  • resultoptionalobject
    2 properties
    • replicaCpuMillicoresoptionalinteger

      CPU in millicores for DB ClickPipes.

      maximum: 32000, minimum: 1000
      Example: 2000
    • replicaMemoryGboptionalnumber

      Memory in GiB for DB ClickPipes. Must be 4× the CPU core count.

      maximum: 128, minimum: 4
      Example: 8
Navigation