[
https://issues.apache.org/jira/browse/BEAM-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826315#comment-16826315
]
yifan zou commented on BEAM-7147:
---------------------------------
the beam4 is offline. The OOM is misleading, it is actually caused by some
thread leaking. A major leak was fixed in
[https://issues.apache.org/jira/browse/BEAM-7109], but seems like there are
still other tests eating the thread pool of the VM. I'll keep beam4 offline for
investigation. You can rerun the test and it could be assigned to a healthy
node.
> Several PR Postcommits failing: java.lang.OutOfMemoryError
> ----------------------------------------------------------
>
> Key: BEAM-7147
> URL: https://issues.apache.org/jira/browse/BEAM-7147
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Daniel Oliveira
> Assignee: yifan zou
> Priority: Major
> Labels: currently-failing
>
> While working on my PR ([PR #6880|https://github.com/apache/beam/pull/8380])
> I tried to run a few Postcommits and got the same error on each one. Not sure
> if this is related to the work being done to move to new machines or
> something else. Can someone help diagnose?
> From this run
> ([https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch_PR/38/]):
> {noformat}
> *17:10:36* Error occurred during initialization of VM
> *17:10:36* java.lang.OutOfMemoryError: unable to create new native thread
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
