hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13789) ForeignException should not be sent to the client
Date Fri, 29 May 2015 22:35:19 GMT

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

Hudson commented on HBASE-13789:

FAILURE: Integrated in HBase-1.2 #117 (See [https://builds.apache.org/job/HBase-1.2/117/])
HBASE-13789 ForeignException should not be sent to the client (matteo.bertozzi: rev 02af4b066f871894b057d26b1ca2b5f031d18735)
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java

> ForeignException should not be sent to the client
> -------------------------------------------------
>                 Key: HBASE-13789
>                 URL: https://issues.apache.org/jira/browse/HBASE-13789
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, master
>    Affects Versions: 2.0.0, 0.98.13,,
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Minor
>         Attachments: HBASE-13789-v0.patch
> ForeignException is in hbase-server so the client will not be able to deserialize it,
and also it will hide the DoNotRetryException of the cause.
> I haven't found an easy way to test it, aside manually looking at the logs. and this
stuff will go away with proc-v2. so for now the easy workaround is catch the ForeignException
in the master which are just the few places related to proc-v1 and throw the cause to the

This message was sent by Atlassian JIRA

View raw message