[
https://issues.apache.org/jira/browse/HDDS-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900731#comment-16900731
]
Elek, Marton commented on HDDS-1912:
------------------------------------
Thank you very much the bug report [~pingsutw] (Especially because
start-ozone/stop-ozone is not tested so frequently)
If I understand well, the problem occurred if you have both hadoop and ozone
install and some of the environment variables (HADOOP_DEFAULT_LIBEXEC_DIR in
this case) has already been set AND points to the hadoop (not ozone) libexec
dir.
Without setting this environment variables the scripts seem to be working.
I have some strange feeling about the patch: it doesn't only include the good
ozone-config.sh, but also sets the HADOOP_HOME and HADOOP_LIBEXEC_DIR. As you
already have a hadoop install it can be confusing.
But as a workaround it seems to be working as the scope of this environment
variables only the ozone-start script.
Long-term we may need to replace all the HADOOP_ environment variable with an
OZONE_ environment variable, but that would be a significant bigger change.
I will commit this patch if no other objections...
> start-ozone.sh fail due to ozone-config.sh not found
> -----------------------------------------------------
>
> Key: HDDS-1912
> URL: https://issues.apache.org/jira/browse/HDDS-1912
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: Ozone CLI
> Affects Versions: 0.5.0
> Reporter: kevin su
> Priority: Major
> Fix For: 0.5.0
>
> Attachments: HDDS-1912.001.patch
>
>
> I want to run Ozone individually,but it will always find start-ozone.sh in
> the *$HAOOP_HOME*/libexec firstly
> If file not found, it will fail
> We should find this file in the both *$HADOOP_HOME* and *$OZONE_HOME*/libexec
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
