Dear All,
We would like to get a vote on this proposal. The implementation is linked to
the KIP, and we have ran this in our production setup for a while.
https://issues.apache.org/jira/browse/KAFKA-12793
Thanks in advance!
//George//
his without support of keyed messages.
>
> Thanks,
>
> Jun
>
>
> On Wed, Mar 24, 2021 at 4:05 AM Guoqiang Shu wrote:
>
> >
> > In our current proposal it can be configured via
> > producer.circuit.breaker.mute.retry.interval (defaulted to 10 mins), b
In our current proposal it can be configured via
producer.circuit.breaker.mute.retry.interval (defaulted to 10 mins), but
perhaps 'interval' is a confusing name.
On 2021/03/23 00:45:23, Guozhang Wang wrote:
> Thanks for the updated KIP! Some more comments inlined.
> >
> > I'm still not sure
Thanks Guozhang for the comments! Again sorry for the very late response. We
took time to further verify the implementation internally and rebased the
proposal on top of our perceived KIP-500 architecture. Embedded please find
some detailed reply.
On 2020/12/15 05:25:13, Guozhang Wang wrote:
er limit. In the extreme case of a
cluster-level failure, the user should be alerted to manually divert
cluster-level traffic to other normal clusters.
> Guozhang
>
>
> On Mon, Dec 14, 2020 at 5:42 PM Guoqiang Shu wrote:
>
> >
> > Hi Jun and Justin,
> >
>
Hi Jun and Justin,
Many thanks for taking a look at our proposal and for the pointer! We learned
about the mechanism proposed to enhance StickyPartitioner. Both methods aim to
exclude brokers with transient errors and prevent cluster wide failure. The
difference lies in the criteria used to t
