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

Hudson commented on HBASE-21890:
--------------------------------

Results for branch branch-2
        [build #1683 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1683/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1683//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1683//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1683//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Use execute instead of submit to submit a task in RemoteProcedureDispatcher
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-21890
>                 URL: https://issues.apache.org/jira/browse/HBASE-21890
>             Project: HBase
>          Issue Type: Bug
>          Components: proc-v2
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 3.0.0, 2.2.0, 2.0.5, 2.3.0, 2.1.4
>
>         Attachments: HBASE-21890-v1.patch, HBASE-21890.patch
>
>
> Found this when implementing HBASE-21875, the UncaughtExceptionHandler will 
> not be invoked if you use submit to submit the task, as by design, you should 
> use the returned Future object to get the result(exception).
> As we do not care the return value here, let's change to use execute method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to