[
https://issues.apache.org/jira/browse/HDFS-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092917#comment-15092917
]
Hadoop QA commented on HDFS-9639:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color}
| {color:red} HDFS-9639 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12781612/HADOOP-12674.001.patch
|
| JIRA Issue | HDFS-9639 |
| Powered by | Apache Yetus 0.2.0-SNAPSHOT http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/14092/console |
This message was automatically generated.
> Inconsistent Logging in BootstrapStandby
> ----------------------------------------
>
> Key: HDFS-9639
> URL: https://issues.apache.org/jira/browse/HDFS-9639
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.7.1
> Reporter: BELUGA BEHR
> Assignee: Xiaobing Zhou
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HADOOP-12674.001.patch
>
>
> {code}
> /* Line 379 */
> if (LOG.isDebugEnabled()) {
> LOG.debug(msg, e);
> } else {
> LOG.fatal(msg);
> }
> {code}
> Why would message, considered "fatal" under most operating circumstances be
> considered "debug" when debugging is on. This is confusing to say the least.
> If there is a problem and the user attempts to debug the situation, they may
> be filtering on "fatal" messages and miss the exception.
> Please consider using only the fatal logging, and including the exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
