Hello Kafka expert,
I am trying to bypass kafka’s default cluster wide partition distribution.
I want to strictly enforce a static plan where all partitions (including
leaders and followers) for specific set of topics should be assigned to a
set of brokers only, regardless of which broker a client use to connect as
bootstrap server. This strategy helps me in DR , patching and also helps
contain the problem to certain brokers without affecting whole cluster
hence reducing blast radius.
*Is it possible to define a custom plan and Kraft controller use it
dynamically during run time for placement of partitions?*
I am looking for a persistent plan that remains as it is even after
restarts and auto rebalances.

Server.properties doesn’t support any such thing.


Regards,
Sunil

Reply via email to