[
https://issues.apache.org/jira/browse/HBASE-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762292#comment-13762292
]
Jesse Yates commented on HBASE-9457:
------------------------------------
bq. The main driving use case are the namespace table and the metrics table.
The namespace jira superceded the systems table jira (HBASE-7999) which was a
subtask for a metrics table (HBASE-7958). Jesse Yates care to chime in?
With metrics, you need to make sure the metrics table was present before you
could be sure the metrics would actually be collected for the primary/user
table. I would imagine the same logic should apply to the security (ACL) table
as well. For metrics, we could drop/buffer info until the table came online,
but wouldn't necessarily work for security.
> 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
