Jeff Kim created KAFKA-10452:
--------------------------------
Summary: Only expire preferred read replica if a leader is alive
for the topic
Key: KAFKA-10452
URL: https://issues.apache.org/jira/browse/KAFKA-10452
Project: Kafka
Issue Type: Bug
Components: clients
Reporter: Jeff Kim
Assignee: Jeff Kim
Fetch from follower functionality periodically expires and refreshes preferred
read replica (at `metadata.max.age.ms` interval). This allows a client to
discover a better follower to fetch from if one becomes available.
However the expiration is done even if the current partition has no leader (can
happen in DR scenario with observers). It makes sense to get the new preferred
replica information and update existing one, instead of expiring existing one
and then fetching new one.
Doing this will allow clients to keep on fetching from a follower/observer
instead of failing to find leader when all ISR replicas go offline.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)