KAFKA-20517: Backport KAFKA-19748 Streams memory-leak note to 4.1 docs#22149
Conversation
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>
|
@AndrewJSchofield do you think this pr to 4.1 branch makes sense ? |
|
|
||
| **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 |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Agree, updated with link /41/getting-started/upgrade/#upgrading-servers-to-401-from-any-version-33x-through-39x.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
I was doubting on it too. Done.
There was a problem hiding this comment.
@muralibasani would you mind filing patch for 4.2, 4.3 and trunk?
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.mdanddocs/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