Hi Luke and Kafka Dev Team,
Any interest in making Kafka Producer non-blocking when Broker is down and
when the metadata refresh cache does not have topic details? This seems to
be a missing piece when it comes to Kafka Producer not being able to handle
state when it is really down vs metadata re
Hi Luke,
Thanks for the pointers.
Sorry for being late I was out.
I would like to propose the following which might be a little different
from the Old one:
Kafka Producer must distinguish between *broker down state* vs *metadata
NOT available* for a given topic.
Like the boot-strap server
Hi Bhavesh,
I understand your point.
There was an old KIP with the similar idea which was not accepted by the
community in the end.
Maybe you can try to bring it back to the community again, or try to
propose your own KIP for this idea?
https://cwiki.apache.org/confluence/display/KAFKA/KIP-286%3A+
Hello Kafka Team,
I would appreciate any insight into how to distinguish between Brocker Down
vs Metadata Refresh not available due to timing issues.
Thanks,
Bhavesh
On Mon, Sep 19, 2022 at 12:50 PM Bhavesh Mistry
wrote:
> Hello Kafka Team,
>
>
>
> We have an environment where Kafka Broker ca
Hello Kafka Team,
We have an environment where Kafka Broker can go down for whatever reason.
Hence, we had configured MAX_BLOCK_MS_CONFIG=0 because we wanted to drop
messages when brokers were NOT available.
Now the issue is we get data loss due to METADATA not being available and
get this
