[
https://issues.apache.org/jira/browse/KAFKA-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jackson Newhouse updated KAFKA-13939:
-------------------------------------
Description: If `loggingEnabled` is false, the `dirtyKeys` Set is not
cleared within `flush()`, see
[https://github.com/apache/kafka/blob/3.2/streams/src/main/java/org/apache/kafka/streams/state/internals/InMemoryTimeOrderedKeyValueBuffer.java#L262.]
However, dirtyKeys is still written to in the loop within `evictWhile`. This
causes dirtyKeys to continuously grow for the life of the buffer. (was: If
`loggingEnabled` is false, the `dirtyKeys` set is not cleared within `flush()`,
see
[https://github.com/apache/kafka/blob/3.2/streams/src/main/java/org/apache/kafka/streams/state/internals/InMemoryTimeOrderedKeyValueBuffer.java#L262.]
However, dirtyKeys is still written to in the loop within `evictWhile`. This
causes dirtyKeys to continuously grow for the life of the buffer. )
> Memory Leak When Logging Is Disabled In InMemoryTimeOrderedKeyValueBuffer
> -------------------------------------------------------------------------
>
> Key: KAFKA-13939
> URL: https://issues.apache.org/jira/browse/KAFKA-13939
> Project: Kafka
> Issue Type: Bug
> Reporter: Jackson Newhouse
> Priority: Major
>
> If `loggingEnabled` is false, the `dirtyKeys` Set is not cleared within
> `flush()`, see
> [https://github.com/apache/kafka/blob/3.2/streams/src/main/java/org/apache/kafka/streams/state/internals/InMemoryTimeOrderedKeyValueBuffer.java#L262.]
> However, dirtyKeys is still written to in the loop within `evictWhile`. This
> causes dirtyKeys to continuously grow for the life of the buffer.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
