Hi Tom,
KIP-455 allows us to distinguish between replication traffic and reassignment
traffic, if the brokers involved have been upgraded to the latest inter-broker
protocol version. Now that KIP-455 has been implemented, it should be possible
to create a quota that does what people actually
Hi Viktor and Colin,
Thanks for the update. Viktor, if you publish your KIP after summit then we
can at least what comes out of the discussion. Distinguishing between
normal ISR traffic and reassignment traffic would be nice (if that's
something your KIP would enable), and any such distinction
Hi Tom, Colin,
I abandoned my KIP because at that time I haven't had time unfortunately to
continue working on it (KIP-248) and I wanted to rework it to remove the
java based client since the admin commands use Scala. Since at that time it
mostly had consensus on the design I think it might be a
Hi Tom,
As you said, there were a few KIPs, but they seem to have become inactive.
It's kind of a tough problem-- probably at least as complex as the admin
interface for ACLs.
There's also the headache of how reassignment quotas should work. We probably
want to change that quota to actually
Hi,
I was wondering, what is the current status of efforts to add an
AdminClient API for managing user quotas? My trawl of the list archives
didn't turn up anything current (KIP-248 was rejected KIP-422 was
discussed), but perhaps I missed something.
Many thanks,
Tom
