You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "chia7712 (via GitHub)" <gi...@apache.org> on 2024/04/01 07:30:11 UTC

Re: [PR] KAFKA-16452: Bound high-watermark offset to range between LLSO and LEO [kafka]

chia7712 commented on PR #15634:
URL: https://github.com/apache/kafka/pull/15634#issuecomment-2029310080

   just curious. Does it happens only if remote storage is enabled? According to the description:
   
   > The follower sends the first FETCH request to the leader, the leader checks whether the isFollowerInSync, then expands the ISR. Also, parks the request in DelayedFetchPurgatory. If the replica was elected as leader before the fetch-response gets processed, then the new-leader will have wrong high-watermark.
   
   It looks like the issue is existent even though we don't use remote storage.


-- 
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-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org