[
https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572003#comment-13572003
]
Sergey Shelukhin commented on HBASE-7649:
-----------------------------------------
Ok, I got back to this, there are two approaches possible.
1) The involved one, we can add RegionOpeningException to HRegionServer, same
place as RegionMovedException. If client gets that he won't remove entry from
cache for some time (say 10 seconds), so it wouldn't go to meta.
2) The hacky, simpler one, purely on client side, after RegionMovedException we
can keep a small delay (if we found out from meta and not RME, we should be
good because meta means it's already opened).
I'd prefer to do (1)... any objections?
> client retry timeout doesn't need to do x2 fallback when going to different
> server
> ----------------------------------------------------------------------------------
>
> Key: HBASE-7649
> URL: https://issues.apache.org/jira/browse/HBASE-7649
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch,
> HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch,
> HBASE-7649-v3.patch
>
>
> See HBASE-7520. When we go to server A, get a bunch of failures, then finally
> learn the region is on B it doesn't make sense to wait for 30 seconds before
> going to B.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
