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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GOBBLIN-770?focusedWorklogId=242157&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-242157 ]

ASF GitHub Bot logged work on GOBBLIN-770:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/May/19 00:37
            Start Date: 15/May/19 00:37
    Worklog Time Spent: 10m 
      Work Description: htran1 commented on pull request #2634: [GOBBLIN-770] Add JVM configuration to avoid exhausting YARN containe…
URL: https://github.com/apache/incubator-gobblin/pull/2634
 
 
   …r memory
   
   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - [X] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-770
   
   
   ### Description
   - [X] Here are some details about my PR, including screenshots (if applicable):
   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.
   
   ### Tests
   - [X] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   
   ### Commits
   - [X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 242157)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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
>          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)