[
https://issues.apache.org/jira/browse/HBASE-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764699#comment-16764699
]
Bahram Chehrazy commented on HBASE-21844:
-----------------------------------------
Yes, there are several Orphan and corrupt ORP and TRSP procedures found by
master at the same time. For this particular TRSP (*pid=44148*) I've foudn
these:
2019-02-08 04:07:51,123 ERROR [master/BN01APA827CE794:16000:becomeActiveMaster]
wal.WALProcedureTree: *Orphan* procedure: Procedure(*pid=44148*, ppid=44140,
class=org.apache.hadoop.hbase.master.assignment.*TransitRegionStateProcedure*)
2019-02-08 04:07:52,635 ERROR
[master/*****************:16000:becomeActiveMaster]
procedure2.ProcedureExecutor: *Corrupt* *pid=44148*, ppid=44140, state=SUCCESS,
hasLock=false; *TransitRegionStateProcedure* table=bachehra_dummy-table,
region=7def9c5afad4e3ca30df4535b5ad4776, ASSIGN
> Master could get stuck in initializing state while waiting for meta
> -------------------------------------------------------------------
>
> Key: HBASE-21844
> URL: https://issues.apache.org/jira/browse/HBASE-21844
> Project: HBase
> Issue Type: Bug
> Components: master, meta
> Affects Versions: 3.0.0
> Reporter: Bahram Chehrazy
> Assignee: Bahram Chehrazy
> Priority: Major
> Attachments:
> 0001-HBASE-21844-Handling-incorrect-Meta-state-on-Zookeep.patch
>
>
> If the active master crashes after meta server dies, there is a slight chance
> of master getting into a state where the ZK says meta is OPEN, but the server
> is dead and there is no active SCP to recover it (perhaps the SCP has aborted
> and the procWALs were corrupted). In this case the waitForMetaOnline never
> returns.
>
> We've seen this happening a few times when there had been a temporary HDFS
> outage. Following log lines shows this state.
>
> 2019-01-17 18:55:48,497 WARN [master/************:16000:becomeActiveMaster]
> master.HMaster: hbase:meta,,1.1588230740 is NOT online; state=
> {1588230740 *state=*OPEN**, ts=1547780128227,
> server=*************,16020,1547776821322}
> ; *ServerCrashProcedures=false*. Master startup cannot progress, in
> holding-pattern until region onlined.
>
> I'm still investigating why and how to prevent getting into this bad state,
> but nevertheless the master should be able to recover during a restart by
> initiating a new SCP to fix the meta.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
