[jira] [Commented] (HDFS-11999) Ozone: Clarify startup error message of Datanode in case namenode is missing
[
https://issues.apache.org/jira/browse/HDFS-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450867#comment-16450867
]
Hudson commented on HDFS-11999:
---
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-11999. Ozone: Clarify startup error message of Datanode in case
(aengineer: rev 14a94e7a4f5b1563b83b6c51a279a9adc781fc64)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockPoolManager.java
> Ozone: Clarify startup error message of Datanode in case namenode is missing
>
>
> Key: HDFS-11999
> URL: https://issues.apache.org/jira/browse/HDFS-11999
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Affects Versions: HDFS-7240
>Reporter: Elek, Marton
>Assignee: Elek, Marton
>Priority: Major
> Fix For: HDFS-7240
>
> Attachments: HDFS-11999-HDFS-7240.001.patch, HDFS-11999.patch
>
>
> Datanode is failing if namenode config setting is missing even for Ozone with
> a confusing error message:
> {code}
> 14:33:29.176 [main] ERROR o.a.h.hdfs.server.datanode.DataNode - Exception in
> secureMain
> java.io.IOException: No services to connect (NameNodes or SCM).
> at
> org.apache.hadoop.hdfs.server.datanode.BlockPoolManager.refreshNamenodes(BlockPoolManager.java:168)
> ~[classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:1440)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.(DataNode.java:510)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2802)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2705)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2752)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2896)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:2920)
> [classes/:na]
> 14:33:29.177 [main] INFO org.apache.hadoop.util.ExitUtil - Exiting with
> status 1: java.io.IOException: No services to connect (NameNodes or SCM).
> {code}
--
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] (HDFS-11999) Ozone: Clarify startup error message of Datanode in case namenode is missing
[
https://issues.apache.org/jira/browse/HDFS-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056626#comment-16056626
]
Anu Engineer commented on HDFS-11999:
-
I will commit this shortly. There is a checkstyle warning issue I will fix it
while committing.
> Ozone: Clarify startup error message of Datanode in case namenode is missing
>
>
> Key: HDFS-11999
> URL: https://issues.apache.org/jira/browse/HDFS-11999
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Affects Versions: HDFS-7240
>Reporter: Elek, Marton
>Assignee: Elek, Marton
> Attachments: HDFS-11999-HDFS-7240.001.patch, HDFS-11999.patch
>
>
> Datanode is failing if namenode config setting is missing even for Ozone with
> a confusing error message:
> {code}
> 14:33:29.176 [main] ERROR o.a.h.hdfs.server.datanode.DataNode - Exception in
> secureMain
> java.io.IOException: No services to connect (NameNodes or SCM).
> at
> org.apache.hadoop.hdfs.server.datanode.BlockPoolManager.refreshNamenodes(BlockPoolManager.java:168)
> ~[classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:1440)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.(DataNode.java:510)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2802)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2705)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2752)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2896)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:2920)
> [classes/:na]
> 14:33:29.177 [main] INFO org.apache.hadoop.util.ExitUtil - Exiting with
> status 1: java.io.IOException: No services to connect (NameNodes or SCM).
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11999) Ozone: Clarify startup error message of Datanode in case namenode is missing
[
https://issues.apache.org/jira/browse/HDFS-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056618#comment-16056618
]
Hadoop QA commented on HDFS-11999:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 21m
43s{color} | {color:green} HDFS-7240 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
15s{color} | {color:green} HDFS-7240 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
45s{color} | {color:green} HDFS-7240 passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
25s{color} | {color:green} HDFS-7240 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
41s{color} | {color:green} HDFS-7240 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
8s{color} | {color:green} HDFS-7240 passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
16s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 48s{color} | {color:orange} hadoop-hdfs-project/hadoop-hdfs: The patch
generated 2 new + 4 unchanged - 0 fixed = 6 total (was 4) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
22s{color} | {color:green} the patch passed {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} findbugs {color} | {color:green} 2m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
5s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 66m 53s{color}
| {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
40s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}107m 21s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure080 |
| | hadoop.hdfs.server.datanode.TestDataNodeErasureCodingMetrics |
| | hadoop.hdfs.server.balancer.TestBalancer |
| Timed out junit tests |
org.apache.hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting |
| | org.apache.hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade |
| | org.apache.hadoop.ozone.container.ozoneimpl.TestRatisManager |
| | org.apache.hadoop.hdfs.TestDFSStripedOutputStreamWithFailure120 |
| | org.apache.hadoop.hdfs.security.token.block.TestBlockToken |
| | org.apache.hadoop.ozone.container.ozoneimpl.TestOzoneContainerRatis |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:14b5c93 |
| JIRA Issue | HDFS-11999 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12873728/HDFS-11999-HDFS-7240.001.patch
|
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux f8f7d88016a1 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | HDFS-7240 / 185e3ad |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| checkstyle |
https://builds.apache.org/job/PreCommit-HDFS-Build/19971/artifact/patchprocess/diff-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
|
| unit |
https://builds.apache.org/job/PreCommit-HDFS-Build/19971/artifact/patchprocess/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
|
| Test Results |
[jira] [Commented] (HDFS-11999) Ozone: Clarify startup error message of Datanode in case namenode is missing
[
https://issues.apache.org/jira/browse/HDFS-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055158#comment-16055158
]
Hadoop QA commented on HDFS-11999:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s{color}
| {color:red} HDFS-11999 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-11999 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12873565/HDFS-11999.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/19958/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Ozone: Clarify startup error message of Datanode in case namenode is missing
>
>
> Key: HDFS-11999
> URL: https://issues.apache.org/jira/browse/HDFS-11999
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Affects Versions: HDFS-7240
>Reporter: Elek, Marton
>Assignee: Elek, Marton
> Attachments: HDFS-11999.patch
>
>
> Datanode is failing if namenode config setting is missing even for Ozone with
> a confusing error message:
> {code}
> 14:33:29.176 [main] ERROR o.a.h.hdfs.server.datanode.DataNode - Exception in
> secureMain
> java.io.IOException: No services to connect (NameNodes or SCM).
> at
> org.apache.hadoop.hdfs.server.datanode.BlockPoolManager.refreshNamenodes(BlockPoolManager.java:168)
> ~[classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:1440)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.(DataNode.java:510)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2802)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2705)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2752)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2896)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:2920)
> [classes/:na]
> 14:33:29.177 [main] INFO org.apache.hadoop.util.ExitUtil - Exiting with
> status 1: java.io.IOException: No services to connect (NameNodes or SCM).
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11999) Ozone: Clarify startup error message of Datanode in case namenode is missing
[
https://issues.apache.org/jira/browse/HDFS-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054830#comment-16054830
]
Anu Engineer commented on HDFS-11999:
-
[~elek] Thanks for the patch, Can you please rename your patch to
HDFS-11999-HDFS-7240.001.patch -- The format is JIRA-BRANCH-patch, otherwise
jenkins will apply this patch on trunk and cause a build failure.
I am +1 on this patch. So please resubmit and I will commit as soon as we have
jenkins run.
Thank you for the contribution.
> Ozone: Clarify startup error message of Datanode in case namenode is missing
>
>
> Key: HDFS-11999
> URL: https://issues.apache.org/jira/browse/HDFS-11999
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
>Affects Versions: HDFS-7240
>Reporter: Elek, Marton
>Assignee: Elek, Marton
> Attachments: HDFS-11999.patch
>
>
> Datanode is failing if namenode config setting is missing even for Ozone with
> a confusing error message:
> {code}
> 14:33:29.176 [main] ERROR o.a.h.hdfs.server.datanode.DataNode - Exception in
> secureMain
> java.io.IOException: No services to connect (NameNodes or SCM).
> at
> org.apache.hadoop.hdfs.server.datanode.BlockPoolManager.refreshNamenodes(BlockPoolManager.java:168)
> ~[classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:1440)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.(DataNode.java:510)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2802)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2705)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2752)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2896)
> [classes/:na]
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:2920)
> [classes/:na]
> 14:33:29.177 [main] INFO org.apache.hadoop.util.ExitUtil - Exiting with
> status 1: java.io.IOException: No services to connect (NameNodes or SCM).
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
