Kamal Chandraprakash created KAFKA-15351:
--------------------------------------------
Summary: Update log-start-offset after leader election for topics
enabled with remote storage
Key: KAFKA-15351
URL: https://issues.apache.org/jira/browse/KAFKA-15351
Project: Kafka
Issue Type: Task
Reporter: Kamal Chandraprakash
In the FETCH response, the leader-log-start-offset will be piggy-backed. But,
there can be a scenario:
# Leader deleted the remote log segment and updates it's log-start-offset
# Before the replica-2 update it's log-start-offset via FETCH-request, the
leadership changed to replica-2.
# There are no more eligible segments to delete from remote.
# The log-start-offset will be stale (referring to old log-start-offset but
the data was already removed from remote)
# If the consumer starts to read from the beginning of the topic, it will fail
to read.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
