Hi, Jose, Thanks for the reply.
Since we are only doing the fast HWM propagation for the KRaft partition, should we remove the changes in Replica manager where the leader will unpark the follower fetch request if its HWM is larger than the follower? Also, followers for non-KRaft partitions probably don't need to set the HWM field. Jun On Fri, May 2, 2025 at 7:48 AM José Armando García Sancio <jsan...@confluent.io.invalid> wrote: > Hi Jun, > > On Thu, May 1, 2025 at 12:38 PM Jun Rao <j...@confluent.io.invalid> wrote: > > We could probably just keep the new HighWatermark field as described in > the > > KIP, but limit it only for KRaft. Also, since HighWatermark is a tagged > > field, it probably doesn't need to be gated by an MV. > > Yes. Because the HighWatermark field is tagged and ignorable, all > version 18 FETCH requests can be serialized to versions 17 requests. > We still need an MV version because the replica fetcher restricts > possible version values using the MV and > FetchRequest.Builder#forReplica builder. > > Thanks, > -- > -José >
