Skip to content

KAFKA-20517: Backport KAFKA-19748 Streams memory-leak note to 4.1 docs#22149

Merged
chia7712 merged 3 commits into
apache:4.1from
muralibasani:KAFKA-20517-backport-19748-note
Apr 27, 2026
Merged

KAFKA-20517: Backport KAFKA-19748 Streams memory-leak note to 4.1 docs#22149
chia7712 merged 3 commits into
apache:4.1from
muralibasani:KAFKA-20517-backport-19748-note

Conversation

@muralibasani
Copy link
Copy Markdown
Contributor

@muralibasani muralibasani commented Apr 25, 2026

Ref : https://issues.apache.org/jira/browse/KAFKA-20517

Backports the KAFKA-19748 Kafka Streams memory-leak warning from trunk (f5a87b3, #20639) to the 4.1 branch.

The original commit did not apply cleanly because trunk's HTML upgrade docs have been migrated to Markdown on 4.1, so the same note is added to docs/getting-started/upgrade.md and docs/streams/upgrade-guide.md.

Wording updated from "when available" to "which includes the fix for it" since 4.1.1 is released.

Reviewers: Erik Skytthe joerg@thalheim.io, Chia-Ping Tsai chia7712@gmail.com

Adapts the trunk commit f5a87b3 (apache#20639) for the 4.1 branch, which
uses Markdown docs instead of the HTML layout on trunk.

Co-authored-by: Shashank <hsshashank.grad@gmail.com>
@muralibasani
Copy link
Copy Markdown
Contributor Author

muralibasani commented Apr 25, 2026

@AndrewJSchofield do you think this pr to 4.1 branch makes sense ?
Related PR https://github.com/apache/kafka/pull/20639/changes

Copy link
Copy Markdown
Member

@chia7712 chia7712 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM


**Note:** Kafka Streams 4.1.0 contains a critical memory leak bug ([KAFKA-19748](https://issues.apache.org/jira/browse/KAFKA-19748)) that affects users of range scans and certain DSL operators (session windows, sliding windows, stream-stream joins, foreign-key joins). Users running Kafka Streams should consider upgrading directly to 4.1.1, which includes the fix for it.

### Upgrading Servers to 4.1.0 from any version 3.3.x through 4.0.x
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could add something here? Leaving the body empty looks a bit weird to me

The rolling upgrade procedure for 4.1.x is identical to the 4.0 upgrade. Please refer to the [Upgrading Servers to 4.0.x](https://www.google.com/search?q=%23) section for detailed step-by-step instructions.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, updated with link /41/getting-started/upgrade/#upgrading-servers-to-401-from-any-version-33x-through-39x.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use #upgrading-servers-to-401-from-any-version-33x-through-39x instead? It's more robust and would be easier to backport to other branches.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was doubting on it too. Done.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@muralibasani would you mind filing patch for 4.2, 4.3 and trunk?

Copy link
Copy Markdown

@eskytthe eskytthe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update to documentation on upgrade looks good to me. Thanks!.
/Erik

@chia7712 chia7712 merged commit ca599e8 into apache:4.1 Apr 27, 2026
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants