Apply a producer byte-rate quota to a specific user: kafka-configs.sh --bootstrap-server localhost:9092 --alter --add-config 'producer_byte_rate=52428800' --entity-type users --entity-name analytics-producer
Apply a consumer byte-rate quota to a client ID: kafka-configs.sh --alter --add-config 'consumer_byte_rate=104857600' --entity-type clients --entity-name reporting-consumer
Combine user and client-ID scope for fine-grained limits: use --entity-type users --entity-name alice --entity-type clients --entity-name app1 in the same command
Set a default quota for all users not explicitly listed: --entity-type users --entity-default --add-config 'producer_byte_rate=10485760'
Quotas are enforced per broker, not cluster-wide; a client producing to multiple brokers is throttled independently on each, so effective cluster-level throughput can be higher than the per-broker quota value
When a client is throttled the broker delays the response (for producers) or reduces the fetch size (for consumers); the client SDK reports a fetch-throttle-time or produce-throttle-time metric that you should alert on
Request-rate quotas (cpu throttling via request_percentage) share the same kafka-configs.sh mechanism but measure network+I/O thread CPU fraction, not bytes
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp