[ 
https://issues.apache.org/jira/browse/HBASE-23171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963634#comment-16963634
 ] 

Hudson commented on HBASE-23171:
--------------------------------

Results for branch branch-2.1
        [build #1695 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1695/]: 
(/) *{color:green}+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/branch-2.1/1695//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1695//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1695//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Ensure region state error messages include server making report (branch-2.1)
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-23171
>                 URL: https://issues.apache.org/jira/browse/HBASE-23171
>             Project: HBase
>          Issue Type: Bug
>          Components: amv2, Operability
>    Affects Versions: 2.1.3
>            Reporter: Michael Stack
>            Assignee: Sean Busbey
>            Priority: Minor
>             Fix For: 2.1.8
>
>
> This message is near useless. A RS is carrying a region that is not known to 
> master but we don't know which server has it because message doesn't say who 
> is complaining (this is fixed in 2.2.x).
> {code}
> 2019-10-14 20:06:50,347 WARN 
> org.apache.hadoop.hbase.master.assignment.AssignmentManager: Failed to 
> checkOnlineRegionsReport, maybe due to network lag, if this message 
> continues, be careful of double assign
> org.apache.hadoop.hbase.exceptions.UnexpectedStateException: Not online: 
> XXXX,ced91598,1570663084277_0001.c727b4ed71a3a29a44cce3a917f753f4.
>       at 
> org.apache.hadoop.hbase.master.assignment.AssignmentManager.checkOnlineRegionsReport(AssignmentManager.java:1014)
>       at 
> org.apache.hadoop.hbase.master.assignment.AssignmentManager.reportOnlineRegions(AssignmentManager.java:973)
>       at 
> org.apache.hadoop.hbase.master.MasterRpcServices.regionServerReport(MasterRpcServices.java:491)
>       at 
> org.apache.hadoop.hbase.shaded.protobuf.generated.RegionServerStatusProtos$RegionServerStatusService$2.callBlockingMethod(RegionServerStatusProtos.java:13139)
>       at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413)
>       at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
>       at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
>       at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to