appchemist commented on PR #15647: URL: https://github.com/apache/kafka/pull/15647#issuecomment-2057454239
> thanks for the PR! just curious, what is the problem without the newly added state? does it cause any issues? @johnnychhsu When a kafka consumer encounters a FENCED_LEADER_EPOCH error or other errors requiring metadata updates, a metadata update is triggered. However, subscription's fetchstate is FETCHING. In this state, the consumer will continuously fetch from the old leader.(because of PreferredReadReplica is reset and metadata is not yet updated) This patch is designed to make consumer wait without sending fetch while metadata is being updated. -- 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
