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 Tue, 23 Feb 2016 17:10:18 GMT

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

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

Thanks, [~saint.ack@gmail.com]!

bq. Doesn't go into branch-1. If you put up a version for branch-1, I'll commit

Will attach one shortly.

> 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
>
>         Attachments: HBASE-15232.001.patch, HBASE-15232.002.patch, HBASE-15232.002.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