[
https://issues.apache.org/jira/browse/AMBARI-24585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24585:
-----------------------------------
Fix Version/s: (was: 2.7.2)
2.7.3
> 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy' is not equal to
> the value of yarn_hierarchy in UI Deploy
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-24585
> URL: https://issues.apache.org/jira/browse/AMBARI-24585
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.7.1
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: Screen Shot 2018-09-02 at 10.20.43 PM.png, Screen Shot
> 2018-09-02 at 10.22.33 PM.png, Screen Shot 2018-09-02 at 10.25.08 PM.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The property 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy'
> does not show up in the UI install wizard even when {{yarn_cgroups_enabled}}
> and {{gpu_module_enabled}} are enabled in YARN configs. But this property is
> available after deployment of the cluster.
> !Screen Shot 2018-09-02 at 10.20.43 PM.png|thumbnail!
> !Screen Shot 2018-09-02 at 10.22.33 PM.png|thumbnail!
> When trying to set a value for the config
> 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy', Stack advisor
> displays the following:
> {code}
> yarn.nodemanager.linux-container-executor.cgroups.hierarchy and
> yarn_hierarchy should always have same value
> yarn.nodemanager.linux-container-executor.cgroups.hierarchy and
> yarn_hierarchy should always have same value
> Name of the Cgroups hierarchy under which all YARN jobs will be launched
> {code}
> !Screen Shot 2018-09-02 at 10.25.08 PM.png|thumbnail!
> From the stack advisor description, looks like
> 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy' property needs
> to be same as yarn_hierarchy. As part of UI Deploy, the property
> {{yarn_hierarchy}} is set to
> {{hadoop-yarn-tmp-ctr-e138-1518143905142-461959-01-000002.hwx.site}}. But
> after deploy, the
> {{yarn.nodemanager.linux-container-executor.cgroups.hierarchy}} is set to
> {{/yarn}} and not the property set while UI Deploy. This is causing Deploy
> failures due to Nodemanagers not getting started. When this property is set
> correctly, Nodemanagers start successfully.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
