[ https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775500#comment-17775500 ]
Guozhang Wang commented on KAFKA-13152: --------------------------------------- At the moment I'm afraid I might become the bottleneck if I took any role as a primary reviewer for large PR / KIPs.. for this ticket, I think [~wcarl...@confluent.io] [~ableegoldman] and also [~lihaosky] has enough background to guide it through. I'm happy to act as a second pair of eyes but I concern not enough committed as a primary reviewer. > Replace "buffered.records.per.partition" & "cache.max.bytes.buffering" with > "{statestore.cache}/{input.buffer}.max.bytes" > ------------------------------------------------------------------------------------------------------------------------- > > Key: KAFKA-13152 > URL: https://issues.apache.org/jira/browse/KAFKA-13152 > Project: Kafka > Issue Type: Improvement > Components: streams > Reporter: Guozhang Wang > Assignee: Sagar Rao > Priority: Major > Labels: kip > Fix For: 3.7.0 > > > The current config "buffered.records.per.partition" controls how many records > in maximum to bookkeep, and hence it is exceed we would pause fetching from > this partition. However this config has two issues: > * It's a per-partition config, so the total memory consumed is dependent on > the dynamic number of partitions assigned. > * Record size could vary from case to case. > And hence it's hard to bound the memory usage for this buffering. We should > consider deprecating that config with a global, e.g. "input.buffer.max.bytes" > which controls how much bytes in total is allowed to be buffered. This is > doable since we buffer the raw records in <byte[], byte[]>. -- This message was sent by Atlassian Jira (v8.20.10#820010)