[
https://issues.apache.org/jira/browse/KAFKA-19748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18027918#comment-18027918
]
ASF GitHub Bot commented on KAFKA-19748:
----------------------------------------
shashankhs11 opened a new pull request, #729:
URL: https://github.com/apache/kafka-site/pull/729
Added a note regarding the memory leak bug in the documentation.
### Preview of `/41/documentation/streams/upgrade-guide`
<img width="1452" height="830" alt="upgrade-guide"
src="https://github.com/user-attachments/assets/fcb52d08-1351-4f03-ad89-baf1b9e8eac0";
/>
### Preview of `/41/documentation/#upgrade`
<img width="1452" height="830" alt="upgrade"
src="https://github.com/user-attachments/assets/1114d3f1-f6ca-4a00-885f-f677d18d4095";
/>
> Memory leak using range scans
> -----------------------------
>
> Key: KAFKA-19748
> URL: https://issues.apache.org/jira/browse/KAFKA-19748
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 4.1.0
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Priority: Blocker
> Fix For: 4.2.0, 4.1.1
>
>
> We introduced a regression bug in AK 4.1.0 release, when range scans are use.
> We are leaking some metrics/sensors.
> Thanks to [~eduwerc] and [~hermankj] for reporting this issue.
> Anybody who is using iterator, ie, any type of all/rang/prefix scan etc is
> affected. Note that certain DSL operators like session-windows,
> sliding-windows, stream-stream joins, and FK-join all use range scans
> internally, so the number of affected users is expected to be quite high.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
