accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3683) Scanner retry time does not back off or include jitter
Date Thu, 19 Mar 2015 03:23:38 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368438#comment-14368438
] 

Josh Elser commented on ACCUMULO-3683:
--------------------------------------

Also, it's common over in hbase-landia to actually include an upper bound on retry logic.
Bringing it up as a point to potentially consider -- it should not be made lightly as it would
have some pretty serious impact in how a client (a user or a server) acts in failure/partition
cases.

> Scanner retry time does not back off or include jitter
> ------------------------------------------------------
>
>                 Key: ACCUMULO-3683
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3683
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>             Fix For: 1.7.0
>
>
> When a tablet server goes down, scans will begin failing. The {{ThriftScanner}} has a
hardcoded 100ms pause between retries.
> There are two things that would improve this: an exponential back-off, and some jitter,
so the tservers aren't hammering the metadata table with requests for the new location at
the same time the master is trying to re-assign the tablets.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message