This is an automated email from the ASF dual-hosted git repository.

damccorm pushed a commit to branch users/damccorm/knownIssue
in repository https://gitbox.apache.org/repos/asf/beam.git


The following commit(s) were added to refs/heads/users/damccorm/knownIssue by 
this push:
     new 72c5e3e24e5 Add blogs
72c5e3e24e5 is described below

commit 72c5e3e24e5dd5cf154e8b7aed0ae23c7bed382e
Author: Danny McCormick <dannymccorm...@google.com>
AuthorDate: Thu Mar 21 04:55:43 2024 -0400

    Add blogs
---
 website/www/site/content/en/blog/beam-2.53.0.md | 9 +++++++++
 website/www/site/content/en/blog/beam-2.54.0.md | 6 +++++-
 2 files changed, 14 insertions(+), 1 deletion(-)

diff --git a/website/www/site/content/en/blog/beam-2.53.0.md 
b/website/www/site/content/en/blog/beam-2.53.0.md
index 14c55956bc1..9a15e86ef3d 100644
--- a/website/www/site/content/en/blog/beam-2.53.0.md
+++ b/website/www/site/content/en/blog/beam-2.53.0.md
@@ -62,6 +62,15 @@ For more information on changes in 2.53.0, check out the 
[detailed release notes
 
 * Upgraded to go 1.21.5 to build, fixing 
[CVE-2023-45285](https://security-tracker.debian.org/tracker/CVE-2023-45285) 
and [CVE-2023-39326](https://security-tracker.debian.org/tracker/CVE-2023-39326)
 
+## Known Issues
+
+* Potential race condition causing NPE in DataflowExecutionStateSampler in 
Dataflow Java Streaming pipelines 
([#29987](https://github.com/apache/beam/issues/29987)).
+* Some Python pipelines that run with 2.52.0-2.54.0 SDKs and use large 
materialized side inputs might be affected by a performance regression. To 
restore the prior behavior on these SDK versions, supply the 
`--max_cache_memory_usage_mb=0` pipeline option. 
([#30360](https://github.com/apache/beam/issues/30360)).
+* Python pipelines that run with 2.53.0-2.54.0 SDKs and perform file 
operations on GCS might be affected by excess HTTP requests. This could lead to 
a performance regression or a permission issue. 
([#28398](https://github.com/apache/beam/issues/28398))
+* In Python pipelines, when shutting down inactive bundle processors, shutdown 
logic can overaggressively hold the lock, blocking acceptance of new work. 
Symptoms of this issue include slowness or stuckness in long-running jobs. 
Fixed in 2.56.0 ([#30679](https://github.com/apache/beam/pull/30679)).
+
+For the most up to date list of known issues, see 
https://github.com/apache/beam/blob/master/CHANGES.md
+
 ## List of Contributors
 
 According to git shortlog, the following people contributed to the 2.53.0 
release. Thank you to all contributors!
diff --git a/website/www/site/content/en/blog/beam-2.54.0.md 
b/website/www/site/content/en/blog/beam-2.54.0.md
index 96210859453..a3d649ec6f3 100644
--- a/website/www/site/content/en/blog/beam-2.54.0.md
+++ b/website/www/site/content/en/blog/beam-2.54.0.md
@@ -61,7 +61,11 @@ For more information on changes in 2.54.0, check out the 
[detailed release notes
 
 ## Known Issues
 
-* N/A
+* Some Python pipelines that run with 2.52.0-2.54.0 SDKs and use large 
materialized side inputs might be affected by a performance regression. To 
restore the prior behavior on these SDK versions, supply the 
`--max_cache_memory_usage_mb=0` pipeline option. 
([#30360](https://github.com/apache/beam/issues/30360)).
+* Python pipelines that run with 2.53.0-2.54.0 SDKs and perform file 
operations on GCS might be affected by excess HTTP requests. This could lead to 
a performance regression or a permission issue. 
([#28398](https://github.com/apache/beam/issues/28398))
+* In Python pipelines, when shutting down inactive bundle processors, shutdown 
logic can overaggressively hold the lock, blocking acceptance of new work. 
Symptoms of this issue include slowness or stuckness in long-running jobs. 
Fixed in 2.56.0 ([#30679](https://github.com/apache/beam/pull/30679)).
+
+For the most up to date list of known issues, see 
https://github.com/apache/beam/blob/master/CHANGES.md
 
 ## List of Contributors
 

Reply via email to