[
https://issues.apache.org/jira/browse/HBASE-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225240#comment-14225240
]
Enis Soztutar commented on HBASE-12570:
---------------------------------------
bq. I'd be in favor of backporting HBASE-10591 to 0.98. Might lead to
surprises, though.
That is why I did not propose that back when I originally did the patch. There
is a way to disable this with a config option. Porting the patch with this
disabled does not make a lot of sense though. We can either bite the bullet, or
not do it in 0.98. I think [~apurtell] can make the call.
> 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)
