[
https://issues.apache.org/jira/browse/HBASE-19341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265212#comment-16265212
]
Anoop Sam John commented on HBASE-19341:
----------------------------------------
Just to add : We have way to abort server now also. CP code throwing any non
IOE , the core will either abort server or remove this CP. This depends on a
config which defaults to a value to say abort server.
Still it would be better to explicitly give a special exception type which will
be handled by server abort(Whatever be the value of the above said config). Or
we should just get rid of this config fully? May be a BC issue. Just we can
deprecate now and remove for 3.0 and there only rely on the Exception type?
WDYT boss?
> Ensure CP can abort a Server
> ----------------------------
>
> Key: HBASE-19341
> URL: https://issues.apache.org/jira/browse/HBASE-19341
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0-beta-1
>
>
> We used to allow a CP pull the Server#abort chain. We removed it in the CP
> refactor. At the end of HBASE-18298, [~an...@apache.org] describes a case
> where Phoenix needs to kill Server in extreme case to maintain consistency.
> This issue is about ensuring that throwing a CPException will indeed kill the
> running server.... Add a test.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
