hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13759) Improve procedure yielding
Date Fri, 29 May 2015 15:51:17 GMT

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

stack commented on HBASE-13759:
-------------------------------

+1

nit: Is state superfluous in below? Doesn't the executor know the 'state' already?

   protected boolean isYieldBeforeExecuteFromState(TEnvironment env, TState state) {


> Improve procedure yielding
> --------------------------
>
>                 Key: HBASE-13759
>                 URL: https://issues.apache.org/jira/browse/HBASE-13759
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2
>    Affects Versions: 2.0.0, 1.2.0
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Trivial
>             Fix For: 2.0.0, 1.2.0
>
>         Attachments: HBASE-13759-v0.patch, HBASE-13759-v1.patch
>
>
> Adds the ability to yield the procedure every execution step.
> by default, a procedure will try to go begin to end without stopping.
> This allows procedures to be nice to other procedures.
> one usage example is ServerShutdownHandler where we want everyone to make some progress.
> Allows procedure to throw InterruptedException, the default handling will be:
> "ask the master if there is an abort of stop. If there is, stop executions and exit.
Else, clear the IE and carryon executing. the interruted procedure will retry".
> If the procedure implementor wants a different behavior, the IE can be catched and custom
handling can be performed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message