[
https://issues.apache.org/jira/browse/HBASE-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rajeshbabu updated HBASE-9241:
------------------------------
Attachment: HBASE-9241_2.patch
Patch addressing Stack's comment.
Moved preMasterInitialization hook before logging(set status) as master
initialized.
@Ram,
bq. Like stop the master from starting - something like that?
If hbase.coprocessor.abortonerror configuration set to true we are aborting
otherwise just logging error. Isn't if fine?
{code}
if
(env.getConfiguration().getBoolean("hbase.coprocessor.abortonerror",false)) {
// server is configured to abort.
abortServer(env, e);
} else {
{code}
> Add cp hook before initialize variable set to true in master intialization
> --------------------------------------------------------------------------
>
> Key: HBASE-9241
> URL: https://issues.apache.org/jira/browse/HBASE-9241
> Project: HBase
> Issue Type: Sub-task
> Components: master
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Attachments: HBASE-9241_2.patch, HBASE-9241.patch
>
>
> This hook helps in following cases.
> 1) When we are creating indexed table then there is a chance that master can
> go down after successful creation of user table but index table creation not
> yet started.
> This hook helps to find such cases and create missing index table.
> 2) if any case there are mismatches in colocation of user and index regions
> we can run balancer.
--
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