showuon commented on PR #12238: URL: https://github.com/apache/kafka/pull/12238#issuecomment-1145703278
> should we allow the broker to be behind by A records (or time) to unfence the broker? I've similar solution came out yesterday, but then, I don't think this is a good solution because it might break the expectation/assumption that when broker is up, the broker should already catch up all the metadata changes. There are chances the `A` records/time behind contain some important metadata update, right? > Another solution is to require the broker to only catch up to the last committed offset when they last sent the heartbeat. I like this idea. We can make sure the broker already catch up the last committed offset when heartbeat sent, which means, the metadata changes before broker startup are all caught up. +1 for it! Thank you. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
