hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5047) [Coprocessors] Implement child failure strategies for external coprocessor host
Date Sun, 11 May 2014 11:08:15 GMT

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

Andrew Purtell updated HBASE-5047:
----------------------------------

    Assignee:     (was: 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
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message