[
https://issues.apache.org/jira/browse/ACCUMULO-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved ACCUMULO-3963.
----------------------------------
Resolution: Fixed
Replaced the (potentially) inaccurate temporal failure implementation (use a
cache with expiration to determine X failures in time T), and use a bounded
linear retry policy.
> Incremental backoff on inability to write to HDFS
> -------------------------------------------------
>
> Key: ACCUMULO-3963
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3963
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.7.0
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Blocker
> Labels: release_notes
> Fix For: 1.7.1, 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ACCUMULO-2480 added some support to kill the tserver if HDFS is unavailable
> after a number of checks. ACCUMULO-3937 added some configuration values to
> loosen this.
> We still only sleep for a static 100ms after every failure. This makes the
> default 15 attempts over 10 seconds a bit misleading as it will kill itself
> after 1.5 seconds not 10.
> I'm thinking that this should really be more like a 30-60s wait period out of
> the box. Anything less isn't really going to insulate operators from
> transient HDFS failures (due to services being restarted or network
> partitions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
