[ https://issues.apache.org/jira/browse/HBASE-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated HBASE-15232: ------------------------------- Attachment: HBASE-15232.001.patch .001 Here's what I was thinking. I was able to piggy-back off of the test added with HBASE-12198 which makes me confident we're doing the right thing. Letting yetus chew on this while I run it through the test suite locally too. > 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)