[
https://issues.apache.org/jira/browse/HBASE-20589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476914#comment-16476914
]
Guanghao Zhang commented on HBASE-20589:
----------------------------------------
2018-05-16 08:31:45,872 INFO [Thread-409] master.HMaster(3604): hbase:meta
deployed at={color:#FF0000}hao-optiplex-7050,44270,1526430656935{color}
2018-05-16 08:31:45,966 INFO [Thread-409] master.ServerManager(596): Processing
expiration of {color:#FF0000}hao-optiplex-7050,41617,1526430656886{color} on
hao-optiplex-7050,36490,1526430656813
2018-05-16 08:31:46,030 INFO
[RpcServer.default.FPBQ.Fifo.handler=3,queue=0,port=36490]
assignment.AssignmentManager(1004): META REPORTED: rit=OPEN,
location=hao-optiplex-7050,44270,1526430656935, table=hbase:meta,
region=1588230740
2018-05-16 08:31:46,030 WARN
[RpcServer.default.FPBQ.Fifo.handler=3,queue=0,port=36490]
assignment.AssignmentManager(1006): META REPORTED but no procedure found
(complete?); set location=hao-optiplex-7050,44270,1526430656935
2018-05-16 08:31:46,039 DEBUG
[RpcServer.default.FPBQ.Fifo.handler=3,queue=0,port=36490]
master.ServerManager(390): Server REPORT rejected; currently processing
hao-optiplex-7050,41617,1526430656886 as dead server
2018-05-16 08:31:46,040 DEBUG
[RpcServer.default.FPBQ.Fifo.handler=3,queue=0,port=36490] ipc.CallRunner(142):
callId: 56 service: RegionServerStatusService methodName: RegionServerReport
size: 389 connection: 127.0.1.1:51136 deadline: 1526430716039,
exception=org.apache.hadoop.hbase.YouAreDeadException: Server REPORT rejected;
currently processing hao-optiplex-7050,41617,1526430656886 as dead server
2018-05-16 08:31:46,044 ERROR [RS:0;hao-OptiPlex-7050:41617]
helpers.MarkerIgnoringBase(159): ***** {color:#FF0000}ABORTING region server
hao-optiplex-7050,41617,1526430656886{color}:
org.apache.hadoop.hbase.YouAreDeadException: Server REPORT rejected; currently
processing hao-optiplex-7050,41617,1526430656886 as dead server
After the meta was assigned to the new RS
hao-optiplex-7050,{color:#FF0000}44270{color},1526430656935, the old RS
hao-optiplex-7050,{color:#FF0000}41617{color},1526430656886 will be aborted
when it report to master. This will make the master initialization cost a long
time.
> Don't need to assign meta to a new RS when standby master become active
> -----------------------------------------------------------------------
>
> Key: HBASE-20589
> URL: https://issues.apache.org/jira/browse/HBASE-20589
> Project: HBase
> Issue Type: Bug
> Reporter: Guanghao Zhang
> Priority: Major
> Attachments: HBASE-20589.master.001.patch
>
>
> I found this problem when I write ut for HBASE-20569. Now the master
> finishActiveMasterInitialization introduce a new
> RecoverMetaProcedure(HBASE-18261) and it has a sub procedure AssignProcedure.
> AssignProcedure will skip assign a region when regions state is OPEN and
> server is online. But for the new regiog state node is created with state
> OFFLINE. So it will assign the meta to a new RS. And kill the old RS when old
> RS report to master. This will make the master initialization cost a long
> time. I will attatch a ut to show this. FYI [~stack]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
