You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:39:11 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 ]

Ethan Rose updated HDDS-1828:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> 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.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org