[
https://issues.apache.org/jira/browse/HBASE-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225456#comment-14225456
]
Andrew Purtell commented on HBASE-12570:
----------------------------------------
I agree backporting sanity checks but disabled by default wouldn't be useful.
Do we need all of them though? We could start with a full backport patch and
remove items that we think might cause issues. Or just address the specific
problem described in this issue (missing class in table config shouldn't take
down the whole regionserver). Either works for me.
> Missing/invalid split policy class name brings down your HBase cluster
> ----------------------------------------------------------------------
>
> 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)
