You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 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.
54
54
55
55
|===
56
56
@@ -100,6 +100,10 @@ endif::[]
100
100
101
101
=== Individual client throughput limit
102
102
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
+
103
107
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`].
104
108
105
109
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
145
149
146
150
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.
147
151
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:
0 commit comments