You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Hui Fei (Jira)" <ji...@apache.org> on 2026/06/09 04:28:04 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 ]
Hui Fei updated HDDS-1828:
--------------------------
Target Version/s: 2.3.0 (was: 2.2.0)
<<Bulk update>>
Apache Ozone 2.2.0 release is in progress. I'm updating all unresolved jiras targeting 2.2.0 to retarget 2.3.0.
> smoke test core-site.xml is confusing to user
> ---------------------------------------------
>
> Key: HDDS-1828
> URL: https://issues.apache.org/jira/browse/HDDS-1828
> Project: Apache Ozone
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org