You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "yifan zou (JIRA)" <ji...@apache.org> on 2019/04/19 17:18:00 UTC
[jira] [Commented] (BEAM-6659) Executor Beam1: can't allocate
memory
[ https://issues.apache.org/jira/browse/BEAM-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822069#comment-16822069 ]
yifan zou commented on BEAM-6659:
---------------------------------
For more details of the OOM issue, see the investigation in https://issues.apache.org/jira/browse/BEAM-7109
> Executor Beam1: can't allocate memory
> -------------------------------------
>
> Key: BEAM-6659
> URL: https://issues.apache.org/jira/browse/BEAM-6659
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Mikhail Gryzykhin
> Assignee: yifan zou
> Priority: Major
> Labels: currently-failing, triaged
> Fix For: Not applicable
>
>
> _Use this form to file an issue for test failure:_
> * [Jenkins Job|https://builds.apache.org/job/beam_PreCommit_Java_Cron/941/consoleFull]
> Initial investigation:
> worker: [beam1|https://builds.apache.org/computer/beam1]
> *10:10:35* >
> *Task :beam-runners-google-cloud-dataflow-java:javadoc*
> FAILED*10:10:35* Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f85d7147000, 858062848, 0) failed; error='Cannot allocate memory' (errno=12)
> ----
> _After you've filled out the above details, please [assign the issue to an individual|https://beam.apache.org/contribute/postcommits-guides/index.html#find_specialist]. Assignee should [treat test failures as high-priority|https://beam.apache.org/contribute/postcommits-policies/#assigned-failing-test], helping to fix the issue or find a more appropriate owner. See [Apache Beam Post-Commit Policies|https://beam.apache.org/contribute/postcommits-policies]._
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)