Skip to content

Commit 4a188b8

Browse files
committed
coderabbit suggestions + add link to API
1 parent 841bc60 commit 4a188b8

1 file changed

Lines changed: 8 additions & 4 deletions

File tree

modules/manage/pages/cluster-maintenance/manage-throughput.adoc

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,13 @@ The properties for broker-wide throughput quota balancing are configured at the
4444
| A broker's total throughput limit for egress Kafka traffic.
4545

4646
| xref:reference:cluster-properties.adoc#kafka_throughput_control[kafka_throughput_control]
47-
| List of clients for whom broker-wide limits do not apply
47+
| List of clients for whom broker-wide limits do not apply.
4848

4949
| xref:reference:cluster-properties.adoc#kafka_throughput_controlled_api_keys[kafka_throughput_controlled_api_keys]
50-
| List of Kafka request types subject to broker-wide throughput limits; defaults to `produce` and `fetch`.
50+
| Kafka request types subject to broker-wide throughput limits; defaults to `produce` and `fetch`.
5151

5252
| xref:reference:tunable-properties.adoc#max_kafka_throttle_delay_ms[max_kafka_throttle_delay_ms]
53-
| The maximum delay inserted in the data path of Kafka API requests to throttle them down. Configuring this to be less than the Kafka client timeout can ensure that the delay that's inserted won't be long enough to cause a client timeout by itself.
53+
| Maximum delay inserted in the data path of Kafka API requests to throttle them down. Setting this lower than the Kafka client timeout helps ensure throttling alone does not cause client timeouts.
5454

5555
|===
5656

@@ -100,6 +100,10 @@ endif::[]
100100

101101
=== Individual client throughput limit
102102

103+
ifdef::env-cloud[]
104+
NOTE: You can also manage client quotas with the link:/api/doc/cloud-dataplane/operation/operation-quotaservice_listquotas[Redpanda Cloud Data Plane API]
105+
endif::[]
106+
103107
To view current throughput quotas set through the Kafka API, run xref:reference:rpk/rpk-cluster/rpk-cluster-quotas-describe.adoc[`rpk cluster quotas describe`].
104108

105109
For example, to see the quotas for client ID `consumer-1`:
@@ -145,7 +149,7 @@ NOTE: A client group specified with `client-id-prefix` is not the equivalent of
145149

146150
You can apply default throughput limits to clients. Redpanda applies the default limits if no quotas are configured for a specific `client_id` or prefix.
147151

148-
To specify a produce quota of 1 GBps through the Kafka API (which means a 1 GBps limit across all produce requests sent to a single Redpanda broker), run:
152+
To specify a produce quota of 1 GB/s through the Kafka API (applies across all produce requests to a single broker), run:
149153

150154
[,bash]
151155
----

0 commit comments

Comments
 (0)