[
https://issues.apache.org/jira/browse/HBASE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268780#comment-13268780
]
Phabricator commented on HBASE-5813:
------------------------------------
Kannan 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:1707 for
efficiency, let's populate this map only if msWaitOnSameRegionLoc > 0.
That for most common cases, i.e. the 1 attempt case, we avoid building this
map.
src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java:1765
could you explain this change: why don't we add these failed requests to the
"failed" list?
REVISION DETAIL
https://reviews.facebook.net/D2847
> 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.10.patch, D2847.11.patch,
> D2847.12.patch, D2847.2.patch, D2847.3.patch, D2847.4.patch, D2847.5.patch,
> D2847.6.patch, D2847.7.patch, D2847.8.patch, D2847.9.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
