Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E292C18E7D for ; Fri, 21 Aug 2015 18:54:47 +0000 (UTC) Received: (qmail 19433 invoked by uid 500); 21 Aug 2015 18:54:47 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 19398 invoked by uid 500); 21 Aug 2015 18:54:47 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 19384 invoked by uid 99); 21 Aug 2015 18:54:47 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2015 18:54:47 +0000 Date: Fri, 21 Aug 2015 18:54:47 +0000 (UTC) From: "Eric Newton (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3963) Incremental backoff on inability to write to HDFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707261#comment-14707261 ] Eric Newton commented on ACCUMULO-3963: --------------------------------------- The main problem was marking up the metadata table with hundreds of empty WALs. Losing a key component, that already has some redundancy built in (HDFS, zookeeper), results in a broken system. Operator headache, sure, but fail-fast is often a better solution than retry-forever. > 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: Critical > Fix For: 1.7.1, 1.8.0 > > > 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)