hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5047) [Coprocessors] Implement child failure strategies for external coprocessor host
Date Thu, 15 Dec 2011 21:47:30 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170512#comment-13170512
] 

Andrew Purtell commented on HBASE-5047:
---------------------------------------

Also need a configurable option to declare laggy children as stuck, a hard response latency
threshold and perhaps also a soft latency threshold with a tolerance factor, e.g. no more
than 3 overages in a minute.
                
> [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 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

        

Mime
View raw message