[
https://issues.apache.org/jira/browse/HBASE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HBASE-5813:
-------------------------------
Attachment: D2847.1.patch
mbautin requested code review of "[jira] [HBASE-5813] [89-fb] Retry immediately
after a NotServingRegionException in a multiput".
Reviewers: Liyin, Kannan, khemani, todd, tedyu, stack, JIRA
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.
TEST PLAN
Run unit tests
REVISION DETAIL
https://reviews.facebook.net/D2847
AFFECTED FILES
src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
MANAGE HERALD DIFFERENTIAL RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/6453/
Tip: use the X-Herald-Rules header to filter Herald messages in your client.
> 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
>
>
> 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
