Hi, thanks for reaching out.
I'd be curious to see whether the memory consumption patterns you observe
change if you switch the memory allocator library.
For example, you could try to use a custom container, install jemalloc and
enable it. See:
Due to the severity of this issue, I am closing the vote on RC1 to produce an
RC2 with the python issue resolved. There will be some other minor cherry picks
done in line with this, and resolving some issues with the Github Actions
That said, this doesn't affect the Java or Go SDKs, so please
Hello!
I'm an avid apache beam user (on Dataflow) and we use beam to stream
blockchain data to various sinks. I recently noticed some memory issues
across all our pipelines but have yet to be able to find the root cause and
was hoping someone on your team might be able to help. If this isn't the
ERROR: File 'src/.test-infra/jenkins/metrics_report/beam-metrics_report.html' does not exist
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/28084 [Bug]: Python
