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:52:18 GMT

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

Josh Elser commented on HBASE-15232:

Ok! Thanks for clarifying. Looks like maybe ClientExceptionUtils also needs to be expanded
in scope?

Concretely, the original symptoms of this were a NotServingRegionException seen by the client
after the multi:

o.a.h.h.c.AsyncProcess [WARN] #10, table=null, attempt=1/0 failed=243ops, last exception:
org.apache.hadoop.hbase.NotServingRegionException: org.apache.hadoop.hbase.NotServingRegionException:
Region <region_name>. is not online on <regionserver_name>

Is this sensible to add NotServingRegionException to {{ClientExceptionsUtil}} as well? Will
add a patch in a moment showing what I'm thinking (based on how ConnectionManager is using

> 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

View raw message