hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15232) Exceptions returned over multi RPC don't automatically trigger region location reloads
Date Fri, 12 Feb 2016 22:23:18 GMT

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

Josh Elser commented on HBASE-15232:
------------------------------------

Oh, it's {{ClientExceptionsUtil}}. Took me a moment :)

Thanks for taking a look, [~eclark]. Let me see if I can address your concerns.

> Exceptions returned over multi RPC don't automatically trigger region location reloads
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-15232
>                 URL: https://issues.apache.org/jira/browse/HBASE-15232
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4
>
>         Attachments: HBASE-15232.001.patch
>
>
> Follow-on for HBASE-15221:
> A work-around was added in HTableMultiplexer to work around an issue that AsyncProcess
wasn't clearing the region location cache on Exception. This was stemming from the issue that
the {{tableName}} is {{null}} because HTableMultiplexer is using the {{multi}} RPC. This causes
an error that looks like:
> {noformat}
> [WARN] Coding error, see method javadoc. row=[B@1673eff, tableName=null
> {noformat}
> HBASE-15221 should fix HTableMultiplexer, but it would be good to push the fix down into
AsyncProcess instead of using higher-level workarounds.



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

Mime
View raw message