[
https://issues.apache.org/jira/browse/HBASE-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16264132#comment-16264132
]
Ankit Singhal commented on HBASE-18298:
---------------------------------------
Thank you [~anoop.hbase] and @Stack for taking a look and suggestions.
bq. You need to abort because you fail to offline an index table? Tell us more.
Actually, when we are unable to write to an Index table , we try to disable the
index by updating the same in our meta table(SYSTEM.CATALOG) so that we will
not attempt any future writes but if we fail to update meta table, to avoid
inconsistency and expecting that writes will not succeed again, we kill the
server so that the edits in the WALs can be replayed on restart.
bq. IIRC, you can throw an exception and we will abort. We can add a test for
this.
yes, we can utilize this.
bq. is config of abort on Exception is to be set false for Phoenix usage? In
such case RS wont get aborted. Only that particular CP will get unloaded
No, we need it to be true. Either we should ensure at Phoenix side that this
config is never set to false on the server or we can have a special exception
from HBase for forceful abort.
Raised PHOENIX-4399 for the same.
> RegionServerServices Interface cleanup for CP expose
> ----------------------------------------------------
>
> Key: HBASE-18298
> URL: https://issues.apache.org/jira/browse/HBASE-18298
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18298.patch, HBASE-18298_V2.patch,
> HBASE-18298_V3.patch, HBASE-18298_V4.patch, HBASE-18298_V5.patch,
> HBASE-18298_V6.patch, HBASE-18298_V7.patch, HBASE-18298_V7.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
