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

Hudson commented on HBASE-15232:
--------------------------------

SUCCESS: Integrated in HBase-1.2-IT #446 (See 
[https://builds.apache.org/job/HBase-1.2-IT/446/])
HBASE-15232 Handle region location cache mgmt in AsyncProcess for (stack: rev 
f502f4ac9b171b8f260b5f4b66caa404227052cd)
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableMultiplexer.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncProcess.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHTableMultiplexerFlushCache.java
* 
hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestHTableMultiplexerViaMocks.java
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/exceptions/ClientExceptionsUtil.java


> 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
>
>         Attachments: HBASE-15232-branch-1.002.patch, 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)

Reply via email to