Change a Managed Kafka cluster's tiered storage settings
Changes whether every topic of an active Managed Kafka cluster is tiered, its days on disk and its disk cap per partition. New days on disk or a new cap applies to the running brokers within minutes, without a restart. It changes the brokers’ defaults, so a topic with its own local.retention.ms or local.retention.bytes keeps them. Turning tiering of every topic on or off wins over each topic’s own choice; the tiered storage sync carries it out. Returns 409 while any change to the cluster is still being applied. Company admins only.
Authorizations
API key passed as a Bearer token in the Authorization header.
Path Parameters
Body
Days on disk: how long tiered topics keep data on broker disks, in ms, from 86400000 (one day) to 1209600000 (14 days).
86400000 <= x <= 1209600000Whether every topic is tiered. It wins over each topic's own choice: turning it on turns tiered storage on for every topic, and turning it off pauses every topic tiered through Artie (one tiered outside Artie, e.g. with the CLI, is left alone). A paused topic keeps new messages on broker disks while what's already in remote storage stays readable until retention expires it.
Disk cap per partition: the most broker disk each partition of a tiered topic keeps, in bytes, at least 1073741824 (1 GiB). Null is no cap.
x >= 1073741824Response
OK
Whether this is a Managed Kafka cluster that Artie runs for the company.
draft, active, deploying, failed, deleted Whether Artie turns tiered storage on for every topic of a Managed Kafka cluster that doesn't choose otherwise.
Whether tiered storage is available on this cluster. Artie turns it on once the cluster's brokers have tiered storage.
When the cluster row last changed. A deploying cluster can be retried 20 minutes after this.
When a deleted Managed Kafka cluster's data is deleted for good. It can be restored until then. Only set while status is deleted.
The step a Managed Kafka cluster's deploy is on. Only set while status is deploying, or failed, where it is the step the deploy stopped at.
applying_custom_resources, issuing_tls_certificate, provisioning_broker_nodes, starting_kafka_brokers, creating_load_balancer Disk cap per partition: the most broker disk each partition of the cluster's tiered topics keeps, in bytes (log.local.retention.bytes). Missing when there is no cap.
Days on disk: how long the cluster's tiered topics keep data on broker disks, in ms (log.local.retention.ms). Missing on clusters made before it, whose brokers use Kafka's default.
A Managed Kafka cluster's configuration. Only set when isManaged, and only by Get a Kafka cluster.
Whether a deleted Managed Kafka cluster is still being taken down. It can't be restored until that finishes. Only set in the clusters list.
Why the last deploy of a Managed Kafka cluster failed. Only set while status is failed.
A Managed Kafka cluster's storage autoscaling. Only set when isManaged.
When the sync last made a Managed Kafka cluster's topics match the tiered storage choice for each. Missing until its first run.

