[
https://issues.apache.org/jira/browse/HBASE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256735#comment-13256735
]
Phabricator commented on HBASE-5813:
------------------------------------
mbautin has commented on the revision "[jira] [HBASE-5813] [89-fb] Retry
immediately after a NotServingRegionException in a multiput".
INLINE COMMENTS
src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java:1736 We
add locations for all regions participating in the query to newRegionLocations
in the initial loop of this function.
src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java:1663
Good catch!
REVISION DETAIL
https://reviews.facebook.net/D2847
BRANCH
retry_immediately_after_a_HBASE-5813_v8
> Retry immediately after a NotServingRegionException in a multiput
> -----------------------------------------------------------------
>
> Key: HBASE-5813
> URL: https://issues.apache.org/jira/browse/HBASE-5813
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
> Assignee: Mikhail Bautin
> Attachments: D2847.1.patch, D2847.2.patch, D2847.3.patch,
> D2847.4.patch, D2847.5.patch
>
>
> After we get some errors in a multiput we invalidate the region location
> cache and wait for the configured time interval according to the backoff
> policy. However, if all "errors" in multiput processing were
> NotServingRegionExceptions, we don't really need to wait. We can retry
> immediately.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
