Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

beam-runners-flink_2.11-job-server:validatesPortableRunner failing due to "insufficient memory" #19186

Closed
kennknowles opened this issue Jun 3, 2022 · 1 comment

Comments

@kennknowles
Copy link
Member

For example,

https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink/231/

https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink/232/

 
05:23:50 Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00007fb1b0689000, 12288, 0) failed; error='Cannot allocate memory' (errno=12)05:23:50 Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00007fbce69aa000, 12288, 0) failed; error='Cannot allocate memory' (errno=12)05:23:50 #05:23:50 # There is insufficient memory for the Java Runtime Environment to continue.05:23:50 # Native memory allocation (mmap) failed to map 12288 bytes for committing reserved memory.05:23:50 # An error report file with more information is saved as:05:23:50 # There is insufficient memory for the Java Runtime Environment to continue.05:23:50 # /home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_PVR_Flink/src/runners/flink/job-server/hs_err_pid24488.log

 

Ankur, did something change recently that would cause Flink portable runner to OOM when running these tests ?

Imported from Jira BEAM-5998. Original Jira may contain additional context.
Reported by: chamikara.

@Abacn
Copy link
Contributor

Abacn commented Jul 27, 2023

obsolete

@Abacn Abacn closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants