nikramakrishnan opened a new pull request, #14649: URL: https://github.com/apache/kafka/pull/14649
In `UnifiedLog.truncateFullyAndStartAt`, local log start offset is not updated after truncating the local log to the given new offset. This means that this offset is not updated when reconstructing the auxiliary state on a follower. If this follower becomes the leader before the local log start offset has had a chance to be updated, reads from any offset between [wrong log start offset; actual log start offset] will be routed on the local storage, which does not contain the corresponding data. Consumer reads will in this case never be satisfied. Changes: - Update the local log start offset of a log after rebuilding the auxiliary state, and update corresponding unit test to verify this. - Add an integration test to exercise the consumption of remote data on a leader that was previously a follower and had rebuilt its auxiliary state from remote storage. ### Committer Checklist (excluded from commit message) - [ ] Verify design and implementation - [ ] Verify test coverage and CI build status -- 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