[
https://issues.apache.org/jira/browse/HBASE-21327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653316#comment-16653316
]
Duo Zhang commented on HBASE-21327:
-----------------------------------
The failed UTs are not related. They are introduced in HBASE-21310 and
HBASE-21311.
For the patch, we can just change the 'map' to 'filter', it should be a typo...
> 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
>
> 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)
