[ 
https://issues.apache.org/jira/browse/YARN-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288803#comment-14288803
 ] 

Tsuyoshi OZAWA commented on YARN-3086:
--------------------------------------

The following is a suggestion from [~rmetzger] in yarn-dev mailing list:
{quote}
If you want to maintain the current value of 4GB as the default value, I
probably need to introduce a new configuration value, similar to:

public static final String YARN_MINICLUSTER_CONTROL_RESOURCE_MONITORING =
    YARN_PREFIX + "minicluster.control-resource-monitoring";

Or is there another approach you would prefer?

I'll add a patch to the JIRA once I've found time to fix it.
{quote}


> Make NodeManager memory configurable in MiniYARNCluster
> -------------------------------------------------------
>
>                 Key: YARN-3086
>                 URL: https://issues.apache.org/jira/browse/YARN-3086
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: test
>            Reporter: Robert Metzger
>            Priority: Minor
>
> Apache Flink has a build-in YARN client to deploy it to YARN clusters.
> Recently, we added more tests for the client, using the MiniYARNCluster.
> One of the tests is requesting more containers than available. This test 
> works well on machines with enough memory, but on travis-ci (our test 
> environment), the available main memory is limited to 3 GB. 
> Therefore, I want to set custom amount of memory for each NodeManager.
> Right now, the NodeManager memory is hardcoded to 4GB.
> As discussed on the yarn-dev list, I'm going to create a patch for this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to