hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9457) Master could fail start if region server with system table is down
Date Mon, 09 Sep 2013 21:28:53 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762325#comment-13762325

Jimmy Xiang commented on HBASE-9457:

For security, the ACL table is assigned just like a user table. It is scanned when it is needed.
If anything is wrong, the operation is retried.  So we don't need it to be available all the
time. It is better to be assigned asap, but it is not mandated. So the master can start up
with no problem if the region server holding ACL dies at this moment.

bq. Don't we have simliar problems with meta? Maybe we can solve it the same way?
For meta, we split meta log for all previouslyFailedServers if log replay is enabled. We don't
want to split log for all failed servers before we say system table is assigned.  For meta,
we have meta server shutdown handler to assign meta again so other regions can be assigned.
If during master restarts, the sever holding a system is dead, we need to specially handle
it otherwise the system table won't be available.

> Master could fail start if region server with system table is down
> ------------------------------------------------------------------
>                 Key: HBASE-9457
>                 URL: https://issues.apache.org/jira/browse/HBASE-9457
>             Project: HBase
>          Issue Type: Bug
>          Components: master, Region Assignment
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Critical
> In the region server holding the system table is killed while master is starting, master
will hang there waiting for system table to be assigned which won't happen.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message