This is an automated email from the ASF dual-hosted git repository. damccorm pushed a commit to branch users/damccorm/known-issues in repository https://gitbox.apache.org/repos/asf/beam.git
commit ecb4a24ec1437a7ac3d73d309b119b0737e7f3c7 Author: Danny McCormick <[email protected]> AuthorDate: Wed Aug 26 15:25:17 2026 -0400 Update CHANGES.md with new known issues Added known issues related to performance regression and memory spikes for Java pipelines. --- CHANGES.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CHANGES.md b/CHANGES.md index 151cbe14aaa..9dbdf80b164 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -204,6 +204,8 @@ * (Java) Projects using the Flink runner with Flink 2.1 or later alongside libraries requiring `org.lz4:lz4-java` (e.g., Kafka clients) may encounter a Gradle capability conflict, because Flink 2.1+ ships `at.yawk.lz4:lz4-java` which declares the same capability. To resolve, add a `capabilitiesResolution` rule to your `build.gradle` that selects `at.yawk.lz4:lz4-java` ([#38947](https://github.com/apache/beam/issues/38947)). * (Python) Long-running Python pipelines might experience memory growth and periodic OOMs ([#39406](https://github.com/apache/beam/issues/39406)). +* (Java) Pipelines with a moderate to heavy Cloud Storage read workload might experience a performance regression ([#39548](https://github.com/apache/beam/issues/39406)). +* (Java) Pipelines using the Dataflow Runner and Java versions 17+ may experience spiky memory caused by a JVM upgrade in the runner image ([#39897](https://github.com/apache/beam/issues/39897). # [2.74.0] - 2026-06-02 @@ -249,6 +251,8 @@ ## Known Issues * (Python) Long-running Python pipelines might experience memory growth and periodic OOMs ([#39406](https://github.com/apache/beam/issues/39406)). +* (Java) Pipelines with a moderate to heavy Cloud Storage read workload might experience a performance regression ([#39548](https://github.com/apache/beam/issues/39406)). +* (Java) Pipelines using the Dataflow Runner and Java versions 17+ may experience spiky memory caused by a JVM upgrade in the runner image ([#39897](https://github.com/apache/beam/issues/39897). # [2.73.0] - 2026-04-29
