[
https://issues.apache.org/jira/browse/KAFKA-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-806.
----------------------------------
Fix Version/s: 3.9.1
3.8.2
Resolution: Fixed
trunk:
https://github.com/apache/kafka/commit/e124d3975bdb3a9ec85eee2fba7a1b0a6967d3a6
4.0: KAFKA-18768
3.9:
https://github.com/apache/kafka/commit/27a3e5560ec8770bc43f97c596604845987ff103
3.8:
https://github.com/chia7712/kafka/commit/f9eb066edb89947c9c822ba8a22f0cdd5b78f2ac
> Index may not always observe log.index.interval.bytes
> -----------------------------------------------------
>
> Key: KAFKA-806
> URL: https://issues.apache.org/jira/browse/KAFKA-806
> Project: Kafka
> Issue Type: Improvement
> Components: log
> Reporter: Jun Rao
> Assignee: PoAn Yang
> Priority: Major
> Labels: newbie++
> Fix For: 4.1.0, 3.9.1, 3.8.2
>
>
> Currently, each log.append() will add at most 1 index entry, even when the
> appended data is larger than log.index.interval.bytes. One potential issue is
> that if a follower restarts after being down for a long time, it may fetch
> data much bigger than log.index.interval.bytes at a time. This means that
> fewer index entries are created, which can increase the fetch time from the
> consumers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
