[
https://issues.apache.org/jira/browse/HBASE-24011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062587#comment-17062587
]
Josh Elser commented on HBASE-24011:
------------------------------------
This isn't a scenario which HBase intends to provide support for. I'll leave
this open for a short while to see if anyone disagrees strongly before closing
this as Won't Fix.
Supporting you and some custom tool you've written to do manual WAL replay is
orthogonal to why your master didn't initialize itself. Maybe there is an
actual bug underneath your request -- but you've not provided enough
information to determine this.
> HMaster does not restart when rsgroup is enabled and /hbase/WALs is moved
> -------------------------------------------------------------------------
>
> Key: HBASE-24011
> URL: https://issues.apache.org/jira/browse/HBASE-24011
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
> Affects Versions: 2.2.3
> Reporter: Mohammad Arshad
> Priority: Critical
>
> HMaster does not restart when rsgroup is enabled and /hbase/WALs is moved
> HMaster restarts properly if rsgroup is not enabled even if /hbase/WALs is
> moved.
> Steps to reproduce:
> # start the cluster
> # create a table do some put, delete
> # kill all the region servers and master
> # move WALs directory for backup (-mv /hbase/WALs /hbase/WALs2)
> # start the cluster
> # Master start fails, initialization keep failing
> {code:java}
> 2020-03-18 11:42:55,369 ERROR
> [ActiveMasterInitializationMonitor-1584511075369] master.HMaster: Master
> failed to complete initialization after 900000ms. Please consider submitting
> a bug report including a thread dump of this process.
> {code}
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
