hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5813) Retry immediately after a NotServingRegionException in a multiput
Date Wed, 18 Apr 2012 01:57:13 GMT

     [ https://issues.apache.org/jira/browse/HBASE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Phabricator updated HBASE-5813:

    Attachment: D2847.5.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

  Adding more logic to handle the case when we get an NSRE but the region location is the
same for one of the regions on a regionserver. It is possible that that region is being reassigned
and the new location has not yet been written to META. In order to avoid exhausting retries
too quickly in that case, we wait for the appropriate amount of time before the retry.

  This will need one more iteration—a request that started as a multi-put might become a
single put during the course of retries, and previous region location needs to be correctly
passed from multi-put to single put.



> 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


View raw message