[
https://issues.apache.org/jira/browse/AMBARI-24981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778399#comment-16778399
]
Hudson commented on AMBARI-24981:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10471 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10471/])
AMBARI-24981. JournalNode may fail to start due to unreadable config
(vishalsuvagia:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=d1c31d9a7a45b37184169a37e0e0296d3fbfd33b])
* (edit)
ambari-agent/src/test/python/resource_management/TestPropertiesFileResource.py
* (edit) ambari-common/src/main/python/ambari_commons/os_utils.py
* (edit)
ambari-agent/src/test/python/resource_management/TestRepositoryResource.py
* (edit) ambari-agent/src/test/python/resource_management/TestFileResource.py
* (edit) ambari-agent/src/test/python/resource_management/TestContentSources.py
* (edit) ambari-common/src/main/python/resource_management/core/sudo.py
* (edit)
ambari-agent/src/test/python/resource_management/TestXmlConfigResource.py
* (edit)
ambari-common/src/main/python/resource_management/core/providers/system.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/providers/repository.py
> JournalNode may fail to start due to unreadable config file
> -----------------------------------------------------------
>
> Key: AMBARI-24981
> URL: https://issues.apache.org/jira/browse/AMBARI-24981
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> During startup, JournalNode reads config files that belong to YARN, not HDFS
> (eg. {{yarn-site.xml}}), if they are present in the Hadoop config dir.
> Ambari's {{File()}} provider creates files at the final location, then sets
> metadata (ownership and permissions). This makes the file visible to other
> processes with possibly the wrong metadata.
> If agent-side parallel execution is enabled, JournalNode may be started
> concurrently with some YARN component. JournalNode may encounter a config
> file that it cannot read, because the file's permissions and owner are still
> 640 and root, respectively, which causes it to shutdown:
> {noformat}
> ERROR conf.Configuration (Configuration.java:loadResource(2999)) - error
> parsing conf yarn-site.xml
> java.io.FileNotFoundException: /etc/hadoop/conf/yarn-site.xml (Permission
> denied)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
