Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 6 Jun 2014 19:08:05 +0000 (UTC)
From: "Bill Havanki (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12718914.1402081603232.83950.1402081685210@arcas>
In-Reply-To: <JIRA.12718914.1402081603232@arcas>
References: <JIRA.12718914.1402081603232@arcas>
Subject: [jira] [Created] (ACCUMULO-2868) Make master configurable in when
 it kills tablet servers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Bill Havanki created ACCUMULO-2868:
--------------------------------------

             Summary: Make master configurable in when it kills tablet servers
                 Key: ACCUMULO-2868
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2868
             Project: Accumulo
          Issue Type: Improvement
          Components: master
    Affects Versions: 1.6.0
            Reporter: Bill Havanki


On a cluster with a flaky network, the master may be unable to contact a tserver for some moderate amount of time and then direct it to terminate, even though the tserver is still up. (See {{gatherTableInformation()}} and {{StatusThread}}. It does not appear possible to configure the master to be more forgiving in these checks. Relevant constants:

* {{DEFAULT_WAIT_FOR_WATCHER}} - interval between server checks
* {{MAX_BAD_STATUS_COUNT}} - the maximum number of failed attempts allowed before killing the tserver

Making one or both of those configurable, or some other pertinent parameter configurable, would allow cluster admins to cope with mild network maladies. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)