You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Hung Tran (JIRA)" <ji...@apache.org> on 2019/05/15 21:10:00 UTC

[jira] [Resolved] (GOBBLIN-770) Add JVM configuration to avoid exhausting YARN container memory

     [ https://issues.apache.org/jira/browse/GOBBLIN-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hung Tran resolved GOBBLIN-770.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.15.0

Issue resolved by pull request #2634
[https://github.com/apache/incubator-gobblin/pull/2634]

> Add JVM configuration to avoid exhausting YARN container memory 
> ----------------------------------------------------------------
>
>                 Key: GOBBLIN-770
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-770
>             Project: Apache Gobblin
>          Issue Type: Task
>            Reporter: Hung Tran
>            Assignee: Hung Tran
>            Priority: Major
>             Fix For: 0.15.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The current code sets Xmx to the value of the YARN container memory limit. The JVM is highly likely to hit the container memory limit with this configuration due to overhead costs that are not in the JVM heap.
> Configuration should be added to set JVM memory as a percentage of the container memory minus a configurable overhead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)