You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/02 19:00:01 UTC
[jira] [Updated] (HDDS-1828) smoke test core-site.xml is confusing
to user
[ https://issues.apache.org/jira/browse/HDDS-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-1828:
--------------------------------
Component/s: test
Target Version/s: 0.7.0
> smoke test core-site.xml is confusing to user
> ---------------------------------------------
>
> Key: HDDS-1828
> URL: https://issues.apache.org/jira/browse/HDDS-1828
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: test
> Reporter: Eric Yang
> Assignee: Xiaoyu Yao
> Priority: Major
>
> In smoke test, Hadoop code is placed in /opt/hadoop, and Ozone code is placed in /opt/ozone.
> There are two copies of core-site.xml, one in $HADOOP_CONF_DIR, and another one in $OZONE_CONF_DIR. When user look at the copy in $OZONE_CONF_DIR, core-site.xml is empty. This may lead to assumption that hadoop is running with local file system. Most application will reference to core-site.xml on the classpath. Hence, it depends on how the application is carefully setup to avoid using $OZONE_CONF_DIR as a single node Hadoop. It may make sense to symlink $OZONE_CONF_DIR to $HADOOP_CONF_DIR to prevent mistakes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org