You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (Assigned) (JIRA)" <ji...@apache.org> on 2011/12/15 22:49:30 UTC
[jira] [Assigned] (HBASE-5047) [Coprocessors] Implement child
failure strategies for external coprocessor host
[ https://issues.apache.org/jira/browse/HBASE-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell reassigned HBASE-5047:
-------------------------------------
Assignee: Andrew Purtell
> [Coprocessors] Implement child failure strategies for external coprocessor host
> -------------------------------------------------------------------------------
>
> Key: HBASE-5047
> URL: https://issues.apache.org/jira/browse/HBASE-5047
> Project: HBase
> Issue Type: Sub-task
> Components: coprocessors
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
>
> There should be three selectable strategies:
> 1. Close and reopen the region, triggering force termination of the stuck child on close, and fork/initialization of a new child on open, along with reinit of all region related resources, other coprocessors, etc.
> 2. Unload/reload the malfunctioning coprocessor. Will require some work in the coprocessor framework to actually support unloading in a reasonable way. The JVM may make this complicated for integrated CPs, so perhaps just for those hosted in external processes.
> 3. Unload/terminate the malfunctioning coprocessor and continue operation. Consider changes in the CP framework for temporary blacklisting, will need that to avoid loading the suspect CP after a split.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira