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

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/12/09 23:21:13 UTC

[jira] [Updated] (HBASE-12570) Improve table configuration sanity checking

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

Andrew Purtell updated HBASE-12570:
-----------------------------------
    Summary: Improve table configuration sanity checking  (was: Missing/invalid split policy class name brings down your HBase cluster)

> Improve table configuration sanity checking
> -------------------------------------------
>
>                 Key: HBASE-12570
>                 URL: https://issues.apache.org/jira/browse/HBASE-12570
>             Project: HBase
>          Issue Type: Bug
>            Reporter: James Taylor
>
> See PHOENIX-1473. If a split policy class cannot be resolved, then your HBase cluster will be brought down as each region server that successively attempts to open the region will not find the class and will bring itself down.
> One idea to prevent this would be to fail the CREATE TABLE or ALTER TABLE admin call if the split policy class cannot be found.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)