chia7712 commented on PR #17870: URL: https://github.com/apache/kafka/pull/17870#issuecomment-3056839932
> Having said that, maybe we can think of a logic to perform a retry in both fetch and share fetch in case the fetchable partitions are not returning enough data from replica manager. there are `fetch.min.bytes` and `fetch.max.wait.ms` which can utilize the normal fetch request I think. > Unlike SFR, fetch requests can fetch from all the partitions. Whether the replica manager provides new data or not, that's a separate discussion. In case of SFR, you don't even make the call to provide data from replica manager for the topic partitions that cannot be acquired. Perhaps the benefit is that we could introduce `PartitionMaxBytesStrategy` to normal fetch request to replace `max.partition.fetch.bytes`? `PartitionMaxBytesStrategy` seems to be more flexible than `max.partition.fetch.bytes` -- 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
