Hi George, I've been looking at the discussion on improving the sticky partitioner, and one of the potential issues we discussed is how we could get information to the partitioner to tell it not to choose certain partitions. Currently, the partitioner can only use availablePartitionsForTopic. I took a quick look at your KIP and it seemed that your KIP would change what partitions are returned with this method. This seems like a step in the right direction for solving that issue too.
I agree with Jun that looking at both of these issues and the proposed solutions would be very helpful. Justine On Tue, Dec 8, 2020 at 10:07 AM Jun Rao <j...@confluent.io> wrote: > Hi, George, > > Thanks for submitting the KIP. There was an earlier discussing on improving > the sticky partitioner in the producer ( > > https://lists.apache.org/thread.html/rae8d2d5587dae57ad9093a85181e0cb4256f10d1e57138ecdb3ef287%40%3Cdev.kafka.apache.org%3E > ). > It seems to be solving a very similar issue. It would be useful to analyze > both approaches and see which one solves the problem better. > > Jun > > On Tue, Dec 8, 2020 at 8:05 AM georgeshu(舒国强) <george...@tencent.com> > wrote: > > > Hello, > > > > We write up a KIP based on a straightforward mechanism implemented and > > tested in order to solve a practical issue in production. > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-693%3A+Client-side+Circuit+Breaker+for+Partition+Write+Errors > > Look forward to hearing feedback and suggestions. > > > > Thanks! > > > > >
