[ https://issues.apache.org/jira/browse/HBASE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phabricator updated HBASE-5813: ------------------------------- Attachment: D2847.12.patch mbautin updated the revision "[jira] [HBASE-5813] [89-fb] Retry immediately after a NotServingRegionException in a multiput". Reviewers: Liyin, Kannan, khemani, todd, tedyu, stack, JIRA, aaiyer Prakash: I think this implements your comments. I moved the logic that decides whether to wait if region locations are the same as before to the point when we already know the new region locations. Re-testing. REVISION DETAIL https://reviews.facebook.net/D2847 AFFECTED FILES src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java src/main/java/org/apache/hadoop/hbase/client/ServerCallable.java src/main/java/org/apache/hadoop/hbase/util/Threads.java > 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