[
https://issues.apache.org/jira/browse/KAFKA-19748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024701#comment-18024701
]
Shashank commented on KAFKA-19748:
----------------------------------
> also update the Kafka web page with a note that people should be
careful and maybe not even upgrade to Kafka Streams 4.1.0.
Hi [~mjsax], I can make a PR for the documentation changes. Would
[upgrade-guide.html|https://github.com/shashankhs11/kafka/blob/trunk/docs/streams/upgrade-guide.html]
be an ideal spot for this note?
> 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)
