You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2013/08/23 15:43:52 UTC
[jira] [Commented] (AMBARI-3004) Categorize YARN properties
properly
[ https://issues.apache.org/jira/browse/AMBARI-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748546#comment-13748546 ]
Aleksandr Kovalenko commented on AMBARI-3004:
---------------------------------------------
+1 for the patch
> Categorize YARN properties properly
> -----------------------------------
>
> Key: AMBARI-3004
> URL: https://issues.apache.org/jira/browse/AMBARI-3004
> Project: Ambari
> Issue Type: Task
> Components: client
> Affects Versions: 1.4.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 1.4.1
>
> Attachments: AMBARI-3004.patch
>
>
> We want to categorize YARN configs better. We need atleast 3 sections:
> * Resource Manager
> * Node Manager
> * Scheduler
> Generally all existing {{yarn.nodemanager.}} properties go into the _Node Manager_ section, and {{yarn.resourcemanager.}} go into _Resource Manager_ section.
> Atleast the following properties should show up in these sections:
> * Resource Manager
> ** yarn.acl.enable
> ** yarn.admin.acl
> ** yarn.log-aggregation-enable
> ** yarn.resourcemanager.webapp.address
> * Scheduler
> ** yarn.resourcemanager.scheduler.class
> ** Capacity Scheduler Configuration
> ** yarn.scheduler.minimum-allocation-mb
> ** yarn.scheduler.maximum-allocation-mb
> * Node Manager
> ** yarn.resourcemanager.nodes.include-path /
> ** yarn.resourcemanager.nodes.exclude-path
> ** yarn.nodemanager.resource.memory-mb
> ** yarn.nodemanager.vmem-pmem-ratio
> ** yarn.nodemanager.log-dirs
> ** yarn.nodemanager.remote-app-log-dir
> ** yarn.nodemanager.remote-app-log-dir-suffix
> ** yarn.nodemanager.aux-services
> ** yarn.nodemanager.log.retain-seconds
> ** yarn.nodemanager.local-dirs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira