hbase-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/HBASE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256990#comment-13256990

Phabricator commented on HBASE-5813:

khemani has commented on the revision "[jira] [HBASE-5813] [89-fb] Retry immediately after
a NotServingRegionException in a multiput".

  The ideal behavior will be the following

  look up cached location
  make the call
  if the call fails with NSRE
    look up cache for location with reload equal to true
    if you get the same location again then
      lookup cache for location with reload equal to <not sure what>
      goto retry
      goto retry

  The difference is that you are not making an extra roundtrip to the region server even when
you have discovered that prevAddress is same as newAddress.



> 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.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


View raw message