You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/12/06 21:24:00 UTC

[jira] [Resolved] (HBASE-19341) Ensure CP can abort a Server

     [ https://issues.apache.org/jira/browse/HBASE-19341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-19341.
---------------------------
      Resolution: Implemented
    Release Note: 
If a procedure throws a non-IOException, e.g. an Error, by default we will abort the hosting server (If hbase.coprocessor.abortonerror is set to false, the non-default, we will not abort -- see HBASE-6873).

See tests in TestRegionServerCoprocessorExceptionWithAbort that verify this facility works.

Resolving as already implemented.

> Ensure CP can abort a Server
> ----------------------------
>
>                 Key: HBASE-19341
>                 URL: https://issues.apache.org/jira/browse/HBASE-19341
>             Project: HBase
>          Issue Type: Improvement
>          Components: Coprocessors
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             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, [~ankit@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)