You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2019/02/15 22:04:00 UTC

[jira] [Updated] (HBASE-21322) Add a scheduleServerCrashProcedure() API to HbckService

     [ https://issues.apache.org/jira/browse/HBASE-21322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated HBASE-21322:
--------------------------------
    Priority: Critical  (was: Major)

> Add a scheduleServerCrashProcedure() API to HbckService
> -------------------------------------------------------
>
>                 Key: HBASE-21322
>                 URL: https://issues.apache.org/jira/browse/HBASE-21322
>             Project: HBase
>          Issue Type: Sub-task
>          Components: hbck2
>            Reporter: Jingyun Tian
>            Assignee: Jingyun Tian
>            Priority: Critical
>             Fix For: 3.0.0, 2.2.0, 2.0.3, 2.1.2
>
>         Attachments: HBASE-21322.branch-2.1.001.patch, HBASE-21322.branch-2.addendum.patch, HBASE-21322.master.001.patch, HBASE-21322.master.002.patch, HBASE-21322.master.003.patch, HBASE-21322.master.004.patch, HBASE-21322.master.005.patch, HBASE-21322.master.006.patch, 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)