[
https://issues.apache.org/jira/browse/AMBARI-12935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723433#comment-14723433
]
Hudson commented on AMBARI-12935:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3352 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3352/])
AMBARI-12935 Ambari is overwriting ownership of yarn.local.dir with yarn:hadoop
in Kerberized cluster (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0e675ff28914f461ec19b0b98539c5e6583cb33e)
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_resourcemanager.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_nodemanager.py
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py
> Ambari is overwriting ownership of yarn.local.dir with yarn:hadoop in
> Kerberized cluster
> ----------------------------------------------------------------------------------------
>
> Key: AMBARI-12935
> URL: https://issues.apache.org/jira/browse/AMBARI-12935
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.1.2
>
> Attachments: AMBARI-12935.patch
>
>
> Ambari is overwriting ownership of yarn.local.dir with yarn:hadoop in
> Kerberized cluster when it should be owned by running user . This happens at
> restart of a nodemanager through Ambari. Only solution was to recreate
> yarn.local.dir at which point it makes correct ownership of files. Restart
> via Ambari then overwrites
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
