Hi Ziming,
Thanks for the reply. It may not be a public interface, yes, but it is
annotated with the @InterfaceStability.Unstable annotation from which I
presumed it'll be public at some point. Therefore in my KIP I proposed to
take it public as we've seen significant interest from our users towar
FWIW, the Wikimedia Foundation would find this change really helpful. We
are going to soon experiment with a stretched Kafka cluster, and it would
be nice to be able to target datacenter AND racks for replica placement.
On Thu, Dec 8, 2022 at 3:37 AM ziming deng wrote:
> Hi Viktor,
>
> As far a
Hi Viktor,
As far as I know, we haven't make ReplicaPlacer a public interface, and we have
no plan to make it public. I think you can submit a discussion or create a JIRA
ticket directly without KIP if you have ideas on improving it, right?
--
Best,
Ziming
> On Nov 29, 2022, at 21:52, Viktor S
Hi All,
I'd like to bump this. I've also updated the KIP to incorporate the new
KRaft changes (ReplicaPlacer). Luckily my proposals were quite similar to
that, so mostly I've made some minor rewording, naming changes, etc.
Again, the brief summary of the KIP:
- expose replica placement strategies
Hey all,
I'd like to propose a new broker side replica assignment strategy and an
interface that generalizes replica assignment on brokers and makes them
pluggable.
Briefly, the motivation for the new replica assignment strategy is that
more and more of our customers would want to run their clust
