[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[ https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597274#comment-16597274 ] Elek, Marton commented on HDDS-222: --- Thanks to check it [~anu]. I have never used start/stop ozone until now. Now I fixed then and seems to be working. I also removed start-all/stop-all (they are for starting hdfs/yarn which is not possible). My impression is that start/stop-ozone doesn't work very well lin some cases (for example by daemons couldn't be stopped) but this is an other issue (see HDDS-214) > 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, HDDS-222.002.patch, > HDDS-222.003.patch, HDDS-222.004.patch > > > As 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595582#comment-16595582
]
Anu Engineer commented on HDDS-222:
---
[~elek]
{code:java}
~/t/o/sbin> ./start-ozone.sh
ERROR: Cannot execute
/Users/aengineer/testDiskBalancer/ozone-0.2.1-SNAPSHOT/sbin/../libexec/hdfs-config.sh.{code}
Not sure if I am doing something wrong. Can you please check?
> 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, HDDS-222.002.patch,
> HDDS-222.003.patch
>
>
> As 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[ https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594285#comment-16594285 ] Ajay Kumar commented on HDDS-222: - Since ozone can sit in parallel with hdfs, i was thinking of avoiding the hdfs/hadoop jars inside ozone. (easier to maintain... patching etc) With both scopes we are having hadoop jars in ozone target dir. So i guess compile scope is ok. > 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, HDDS-222.002.patch > > > As 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588500#comment-16588500
]
Elek, Marton commented on HDDS-222:
---
I prefer to change all the dependencies to compile level unless we have a
strong reason to keep it on provided. According to the maven nomenclature they
should be compile scope anyway. Provided was used just as a workaround (IMHO).
According to this page:
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
{quote}provided: This is much like compile, but indicates you expect the JDK
or a container to provide the dependency at runtime. For example, when building
a web application for the Java Enterprise Edition, you would set the dependency
on the Servlet API and related Java EE APIs to scope provided because the web
container provides those classes{quote}
I think it's not our use case. We need the dependencies and the jars should be
there.
Compile time dependency also helps a lot to start the service components from
IDE.
> 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, HDDS-222.002.patch
>
>
> As 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[ https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584446#comment-16584446 ] Ajay Kumar commented on HDDS-222: - [~elek] thanks for updating the patch. Tested locally, build was successful along with acceptance test. Alternatively we can keep the dependencies as provided and export them in ozone classpath inside ozone-config.sh? > 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, HDDS-222.002.patch > > > As 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[ https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16572211#comment-16572211 ] Elek, Marton commented on HDDS-222: --- The problem was the provided dependency in the maven pom files. With normal compile time dependency all the required files are copied to the share/... folder. > 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, HDDS-222.002.patch > > > As 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543307#comment-16543307
]
Nanda kumar commented on HDDS-222:
--
[~anu] & [~elek], the acceptance test is failing for me as well.
I also tried to deploy a pseudo-distributed cluster with this patch, got the
below error while starting scm
{noformat}
apache/ozone-0.2.1-SNAPSHOT> bin/ozone scm
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/hadoop/hdfs/DFSUtil
at
org.apache.hadoop.hdds.scm.server.StorageContainerManager.main(StorageContainerManager.java:275)
Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.hdfs.DFSUtil
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 1 more
{noformat}
It looks like the classpath is not properly set or we are not properly copying
the required jar files.
> 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
>
>
> As 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540644#comment-16540644
]
Anu Engineer commented on HDDS-222:
---
Even after the revert, I am running into the same issue after this patch is
applied.
Here is the command that I am using to build.
_mvn package -Pdist -Phdds -DskipTests -Dtar -DskipShade
-Dmaven.javadoc.skip=true_
Here is the error message:
{noformat}
Acceptance.Basic.Ozone-Shell :: Test ozone shell CLI usage| FAIL |
Suite setup failed:
Keyword 'Is Daemon started' failed after retrying for 1 minute. The last error
was: 'Attaching to basic_ozoneManager_1, basic_datanode_1, basic_scm_1
ozoneManager_1 | Waiting 15 seconds for SCM startup
ozoneManager_1 | Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/hadoop/hdfs/DFSUtil
ozoneManager_1 | at
org.apache.hadoop.ozone.om.OzoneManager.main(OzoneManager.java:303)
ozoneManager_1 | Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.hdfs.DFSUtil
ozoneManager_1 | at
java.net.URLClassLoader.findClass(URLClassLoader.java:381)
ozoneManager_1 | at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
ozoneManager_1 | at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
ozoneManager_1 | at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
ozoneManager_1 | ... 1 more
scm_1 | Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/hadoop/hdfs/DFSUtil
[ Message content over the limit has been removed. ]
datanode_1 | 2018-07-11 20:46:28 ERROR HddsDatanodeService:249 - Exception
in HddsDatanodeService.
datanode_1 | java.lang.NoClassDefFoundError: org/apache/hadoop/hdfs/DFSUtil
datanode_1 | at
org.apache.hadoop.ozone.HddsDatanodeService.main(HddsDatanodeService.java:234)
datanode_1 | Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.hdfs.DFSUtil
datanode_1 | at
java.net.URLClassLoader.findClass(URLClassLoader.java:381)
datanode_1 | at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
datanode_1 | at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
datanode_1 | at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
datanode_1 | ... 1 more
datanode_1 | 2018-07-11 20:46:28 INFO ExitUtil:210 - Exiting with status
1: java.lang.NoClassDefFoundError: org/apache/hadoop/hdfs/DFSUtil' does not
contain 'HTTP server of OZONEMANAGER is listening'
{noformat}
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[ https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540524#comment-16540524 ] Anu Engineer commented on HDDS-222: --- Hold on, I am reverting HDFS-242. [~nandakumar131] FYI and I will recommit after I fix the issues. > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[ https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540457#comment-16540457 ] Anu Engineer commented on HDDS-222: --- +1, thanks it worked for me too. I did a clean of the repo and did a rebuild with -pdist. Thanks for the patch. I will commit it shortly. > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540019#comment-16540019
]
Elek, Marton commented on HDDS-222:
---
Thanks [~anu] to check it.
Yes, it should work after a dist build. I checked it again and it worked for
me. ozone-config.sh is part of the patch.
Could you please check if you have the config file? For me, it's in the right
dirs:
{code:java}
find -name ozone-config.sh
./hadoop-ozone/common/src/main/bin/ozone-config.sh
./hadoop-ozone/common/target/hadoop-ozone-common-0.2.1-SNAPSHOT/libexec/ozone-config.sh
./hadoop-ozone/common/target/hadoop-ozone-common-0.2.1-SNAPSHOT/sbin/ozone-config.sh
./hadoop-dist/target/ozone/libexec/ozone-config.sh
./hadoop-dist/target/ozone/sbin/ozone-config.sh
{code}
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539509#comment-16539509
]
Anu Engineer commented on HDDS-222:
---
On my machine acceptance-tests are failing.
{noformat}
scm_1 | ERROR: Cannot execute
/opt/hadoop/bin/../libexec/ozone-config.sh.
ozoneManager_1 | Waiting 15 seconds for SCM startup
ozoneManager_1 | ERROR: Cannot execute
/opt/hadoop/bin/../libexec/ozone-config.sh.' does not contain 'HTTP server of
OZONEMANAGER is listening'
{noformat}
Am I missing something step ?
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[
https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537253#comment-16537253
]
genericqa commented on HDDS-222:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
21s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
27s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 26m
42s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 27m
31s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
9m 36s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
25s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 34m
13s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} shellcheck {color} | {color:red} 0m
34s{color} | {color:red} The patch generated 2 new + 0 unchanged - 0 fixed = 2
total (was 0) {color} |
| {color:orange}-0{color} | {color:orange} shelldocs {color} | {color:orange}
0m 10s{color} | {color:orange} The patch generated 2 new + 114 unchanged - 0
fixed = 116 total (was 114) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
9m 56s{color} | {color:green} patch has no errors when building and testing our
client artifacts. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 35m
25s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
47s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}146m 46s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:abb62dd |
| JIRA Issue | HDDS-222 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12930849/HDDS-222.001.patch |
| Optional Tests | asflicense shellcheck shelldocs mvnsite unit |
| uname | Linux 230fa4f0e974 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14
08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / eecb5ba |
| maven | version: Apache Maven 3.3.9 |
| shellcheck | v0.4.6 |
| shellcheck |
https://builds.apache.org/job/PreCommit-HDDS-Build/469/artifact/out/diff-patch-shellcheck.txt
|
| shelldocs |
https://builds.apache.org/job/PreCommit-HDDS-Build/469/artifact/out/diff-patch-shelldocs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HDDS-Build/469/testReport/ |
| Max. process+thread count | 410 (vs. ulimit of 1) |
| modules | C: hadoop-ozone/common . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HDDS-Build/469/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> 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
[jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
[ https://issues.apache.org/jira/browse/HDDS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536970#comment-16536970 ] Elek, Marton commented on HDDS-222: --- The only dependency between the ozone shell script and the hdfs scripts was the hdfs-config.sh. I cloned it as ozone-config.sh. Tested with the acceptance tests. > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
