Thanks Neha. I'll discard this for now. We can pick it up once replica
throttling and the default policies are available and tested.
On Thu, Feb 11, 2016 at 5:45 PM, Neha Narkhede wrote:
> >
> > 1. Replica Throttling - I agree this is rather important to get done.
> > However, it may also be arg
>
> 1. Replica Throttling - I agree this is rather important to get done.
> However, it may also be argued that this problem is orthogonal. We do not
> have these protections currently yet we do run partition reassignment
> fairly often. Having said that, I'm perfectly happy to tackle KIP-46 after
Hi Neha,
Thanks for the detailed reply and apologies for my late response. I do have
a few comments.
1. Replica Throttling - I agree this is rather important to get done.
However, it may also be argued that this problem is orthogonal. We do not
have these protections currently yet we do run parti
Adi,
Thanks for the write-up. Here are my thoughts:
I think you are suggesting a way of automating resurrecting a topic’s
replication factor in the presence of a specific scenario: in the event of
permanent broker failures. I agree that the partition reassignment
mechanism should be used to add r
Hey everyone,
I just created a kip to discuss automated replica reassignment when we lose
a broker in the cluster.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-46%3A+Self+Healing+Kafka
Any feedback is welcome.
Thanks,
Aditya
