[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450767#comment-16450767
]
Hudson commented on HDFS-11849:
---
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-11849. JournalNode startup failure exception should be logged in (xyao:
rev 9b09503c8b102dad624d825a7037f68081da2794)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/JournalNode.java
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
>Priority: Major
> Fix For: 2.9.0, 2.7.4, 3.0.0-alpha4, 2.8.2
>
> Attachments: HDFS-11849-001.patch, HDFS-11849-002.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
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-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023124#comment-16023124
]
Brahma Reddy Battula commented on HDFS-11849:
-
Pushed to {{branch-2.8}} too.
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
> Fix For: 2.9.0, 2.7.4, 3.0.0-alpha3, 2.8.1, 2.8.2
>
> Attachments: HDFS-11849-001.patch, HDFS-11849-002.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020531#comment-16020531
]
Surendra Singh Lilhore commented on HDFS-11849:
---
Thanks [~brahmareddy] for review and commit.
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
> Fix For: 2.9.0, 2.7.4, 3.0.0-alpha3, 2.8.1
>
> Attachments: HDFS-11849-001.patch, HDFS-11849-002.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020099#comment-16020099
]
Hudson commented on HDFS-11849:
---
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11765 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11765/])
HDFS-11849. JournalNode startup failure exception should be logged in (brahma:
rev 9cab42cc797986081fef184748044f1790a4f039)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/JournalNode.java
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
> Fix For: 2.9.0, 2.7.4, 3.0.0-alpha3, 2.8.1
>
> Attachments: HDFS-11849-001.patch, HDFS-11849-002.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019312#comment-16019312
]
Hadoop QA commented on HDFS-11849:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
22s{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} 14m
25s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
56s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
38s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
2s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
47s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
41s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s{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} 1m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 88m 7s{color}
| {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
20s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}115m 23s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure080 |
| | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure140 |
| | hadoop.hdfs.server.balancer.TestBalancer |
| | hadoop.hdfs.TestDFSRSDefault10x4StripedOutputStreamWithFailure |
| | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure070 |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:14b5c93 |
| JIRA Issue | HDFS-11849 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12869202/HDFS-11849-002.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 0e490881af03 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31
14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / fcbdecc |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| unit |
https://builds.apache.org/job/PreCommit-HDFS-Build/19536/artifact/patchprocess/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HDFS-Build/19536/testReport/ |
| modules | C: hadoop-hdfs-project/hadoop-hdfs U:
hadoop-hdfs-project/hadoop-hdfs |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/19536/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> JournalNode startup
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019204#comment-16019204
]
Brahma Reddy Battula commented on HDFS-11849:
-
Thanks for updating the patch, +1 on latest patch. Pending for jenkins.
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
> Attachments: HDFS-11849-001.patch, HDFS-11849-002.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019194#comment-16019194
]
Surendra Singh Lilhore commented on HDFS-11849:
---
Thanks [~vinayrpet] and [~brahmareddy] for review..
Attached updated patch, Please review..
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
> Attachments: HDFS-11849-001.patch, HDFS-11849-002.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018705#comment-16018705
]
Brahma Reddy Battula commented on HDFS-11849:
-
[~surendrasingh] thanks for the patch.
bq. 337 System.exit(-1);
can we use ExitUtil.terminate(..)..?
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
> Attachments: HDFS-11849-001.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017305#comment-16017305
]
Vinayakumar B commented on HDFS-11849:
--
+1
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
> Attachments: HDFS-11849-001.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016173#comment-16016173
]
Hadoop QA commented on HDFS-11849:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
14s{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} 12m
58s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
48s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
33s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
50s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
41s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
39s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s{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} 1m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 64m 35s{color}
| {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
15s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 89m 25s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hdfs.web.TestWebHdfsTimeouts |
| | hadoop.hdfs.TestDFSRSDefault10x4StripedOutputStreamWithFailure |
| | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure080 |
| | hadoop.hdfs.server.datanode.TestDataNodeErasureCodingMetrics |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:14b5c93 |
| JIRA Issue | HDFS-11849 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12868787/HDFS-11849-001.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 658045a89e44 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 | trunk / ba70225 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| unit |
https://builds.apache.org/job/PreCommit-HDFS-Build/19493/artifact/patchprocess/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HDFS-Build/19493/testReport/ |
| modules | C: hadoop-hdfs-project/hadoop-hdfs U:
hadoop-hdfs-project/hadoop-hdfs |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/19493/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> JournalNode startup failure exception should be logged in log file
>
[jira] [Commented] (HDFS-11849) JournalNode startup failure exception should be logged in log file
[
https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016012#comment-16016012
]
Surendra Singh Lilhore commented on HDFS-11849:
---
Attached initial patch.
Please review..
> JournalNode startup failure exception should be logged in log file
> --
>
> Key: HDFS-11849
> URL: https://issues.apache.org/jira/browse/HDFS-11849
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: journal-node
>Affects Versions: 2.7.0
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
> Attachments: HDFS-11849-001.patch
>
>
> JournalNode failed to start because of kerberos login.
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for
> xxx/y...@.com from keytab dummy.keytab:
> javax.security.auth.login.LoginException: host1
> at
> org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG: java = 1.x.x
> /
> 2017-05-18 16:08:14,961 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal
> handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
> loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period
> at 10 second(s).
> 2017-05-18 16:08:15,660 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system
> started
> 2017-05-18 16:08:16,429 INFO
> org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> /
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
