[
https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143020#comment-15143020
]
Josh Elser commented on HBASE-15232:
------------------------------------
Ok, cool. Thanks [~stack]. I haven't been keeping up like I should. I
appreciate you taking a look.
bq. Patch LGTM. Whats all the removal in TestHTableMultiplexerViaMocks about?
They are removal of some tests I add in the parent, HBASE-15221. Essentially
this is an addendum-esque fix, but put into a separate issue (per [~busbey]'s
request to avoid a weird split if the current 1.2.0 RC passes). The test
methods removed in that class were specifically for my original fix to the bug,
but are now unnecessary with the proper (IMO) fix to the bug in AsyncProcess
instead of farther up in HTableMultiplexer.
> 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)
