[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540484#comment-16540484
]
Anu Engineer commented on HDDS-222:
-----------------------------------
I think I found the issue. while I committed this patch
{noformat}
commit a47ec5dac4a1cdfec788ce3296b4f610411911ea
Author: Anu Engineer <[email protected]>
Date: Tue Jul 10 15:58:47 2018 -0700
HDDS-242. Introduce NEW_NODE, STALE_NODE and DEAD_NODE event
and corresponding event handlers in SCM.
Contributed by Nanda Kumar.{noformat}
I accidentally committed {{hadoop-ozone/common/src/main/bin/ozone-config.sh}}.
I was trying to amortize the cost of acceptance tests by batching patches.
Then it is did not work and I reverted the tree, somehow this file was not
reset. So [~elek] can you please rebase this patch – probably just remove the
ozone-config.sh from the patch and see if that is working ? I don't want to
revert since it might be easier to fix this mistake in this patch. Thanks for
the help and sorry about the goof up.
> Remove hdfs command line from ozone distrubution.
> -------------------------------------------------
>
> Key: HDDS-222
> URL: https://issues.apache.org/jira/browse/HDDS-222
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: newbie
> Fix For: 0.2.1
>
> Attachments: HDDS-222.001.patch
>
>
> Az the ozone release artifact doesn't contain a stable namenode/datanode code
> the hdfs command should be removed from the ozone artifact.
> ozone-dist-layout-stitching also could be simplified to copy only the
> required jar files (we don't need to copy the namenode/datanode server side
> jars, just the common artifacts
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
