[
https://issues.apache.org/jira/browse/HBASE-21322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654226#comment-16654226
]
stack commented on HBASE-21322:
-------------------------------
bq. delete all MasterProcWALs immediately.
Do you delete while the Master is up?
bq. 3. check if the cluster can fail over.
You mean, have Master fail over?
The scenario you describe is extreme. The new Master does not pick up the
-splitting items? Or it skips them because it notices that the cluster is 'up'?
I do not have an objection to being able to schedule an SCP. It could be
useful. I'm trying to figure what the real world scenario you are simulating
is... and why a new Master coming online doesn't recognize need for an SCP.
Thanks.
> Add a scheduleServerCrashProcedure() API to HbckService
> -------------------------------------------------------
>
> Key: HBASE-21322
> URL: https://issues.apache.org/jira/browse/HBASE-21322
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
> Attachments: Screenshot from 2018-10-17 13-35-58.png, Screenshot from
> 2018-10-17 13-38-41.png, Screenshot from 2018-10-17 13-47-06.png
>
>
> According to my test, if one RS is down, then all procedure logs are deleted,
> it will lead to that no ServerCrashProcedure is scheduled. And restarting
> master cannot help. Thus we need to schedule a ServerCrashProcedure manually
> to solve the problem. I plan to add a scheduleServerCrashProcedure() API to
> HbckService, then add this API to HBCK2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
