Hey Ivan, Thanks for the KIP. Some questions for clarification: It seems like the main problem is that if we don't poll frequently enough, the cluster topology can change entirely before the metadata is refreshed and thus causing staled clients. My question is: if you don't use the client for a long time, why can't you just close the client and re-instantiate a new one when needed? I'm not familiar with the stream thread, so I don't know if that's possible. Another idea here is, would it make sense to expose a maybeUpdateMetadata() API to serve such a purpose?
Thanks, P On Wed, Jan 18, 2023 at 4:07 AM Ivan Yurchenko <ivan0yurche...@gmail.com> wrote: > Hello! > I would like to start the discussion thread on KIP-899: Allow clients to > rebootstrap. > This KIP proposes to allow Kafka clients to repeat the bootstrap process > when fetching metadata if none of the known nodes are available. > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-899%3A+Allow+clients+to+rebootstrap > > A question right away: should we eventually change the default behavior or > it can remain configurable "forever"? The latter is proposed in the KIP. > > Thank you! > > Ivan >
