...
Configuration Management
We need a mechanism to configure the default quotas and the per-user overrides. There is general agreement that we eventually need dynamic configs per-user to fully operationalize quotas but for the purposes of this proposal, we will proceed with static configs.
Code Block |
---|
// Default bytes-out per consumer. quota.consumer.default=2M quota.producer.default=2M // Overrides quota.producer.override="clientA:4M;clientB:10M" quota.consumer.override="clientC:3M;clientD:5M" |
There is a separate discussion for dynamic configs per-user that isn't fully fleshed out. If it makes sense and people agree on a final design, we can model quotas using it.
Tooling/Monitoring Changes
Upon implementation, we will start exposing per-client byte rate metrics metrics to JMX. Since these are new metrics there are no backward compatibility issues. These metrics will be documented prior to the release.
Client Status Code
Compatibility, Deprecation, and Migration Plan
...