[
https://issues.apache.org/jira/browse/HBASE-21327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655124#comment-16655124
]
Hudson commented on HBASE-21327:
--------------------------------
Results for branch master
[build #553 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/553/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/553//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/553//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/553//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Fix minor logging issue where we don't report servername if no associated SCP
> -----------------------------------------------------------------------------
>
> Key: HBASE-21327
> URL: https://issues.apache.org/jira/browse/HBASE-21327
> Project: HBase
> Issue Type: Bug
> Components: amv2
> Reporter: stack
> Assignee: stack
> Priority: Trivial
> Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21327.branch-2.1.001.patch
>
>
> When reporting on whether an associated SCP, this is what we log:
> {code}
> 2018-10-16 14:05:57,607 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,607 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,607 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,607 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: true has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> 2018-10-16 14:05:57,608 ERROR
> org.apache.hadoop.hbase.master.RegionServerTracker: false has no matching
> ServerCrashProcedure
> {code}
> i.e. we are supposed to log servername but we don't. Minor issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
