Return-Path: 
 <notifications-return-23590-apmail-accumulo-notifications-archive=accumulo.apache.org@accumulo.apache.org>
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 E1E3911E2B
	for <apmail-accumulo-notifications-archive@minotaur.apache.org>;
 Tue, 12 Aug 2014 18:47:13 +0000 (UTC)
Received: (qmail 98756 invoked by uid 500); 12 Aug 2014 18:47:13 -0000
Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org
Received: (qmail 98724 invoked by uid 500); 12 Aug 2014 18:47:13 -0000
Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@accumulo.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@accumulo.apache.org>
List-Post: <mailto:notifications@accumulo.apache.org>
List-Id: <notifications.accumulo.apache.org>
Reply-To: jira@apache.org
Delivered-To: mailing list notifications@accumulo.apache.org
Received: (qmail 98707 invoked by uid 99); 12 Aug 2014 18:47:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Aug 2014 18:47:13 +0000
Date: Tue, 12 Aug 2014 18:47:13 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12648969.1369258589579.65550.1407869233425@arcas>
In-Reply-To: <JIRA.12648969.1369258589579@arcas>
References: <JIRA.12648969.1369258589579@arcas>
Subject: [jira] [Commented] (ACCUMULO-1454) Need good way to perform a
 rolling restart of all tablet servers
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-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094482#comment-14094482 ] 

Josh Elser commented on ACCUMULO-1454:
--------------------------------------

bq. start a lot of new tserver instances

This might be more difficult than it sounds. {{start-server.sh}} is fairly easy to manage, but {{stop-server.sh}} is pretty aggressive about just {{kill}}'ing the process on a host. I think we might have to expand on the shell scripts to really give an admin what they want.

bq. migrate tablets <tserver instance src> <tserver instance dest>

Would you consider this a FATE op that the master coordinates, or would you just add something directly to the TServer and let the client handle the coordination? Would that just bash ZooKeeper trying to migrate tablets off of ~200 tservers? (e.g. 200 tservers * 200 tablets)?

> Need good way to perform a rolling restart of all tablet servers
> ----------------------------------------------------------------
>
>                 Key: ACCUMULO-1454
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1454
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>    Affects Versions: 1.4.3, 1.5.0
>            Reporter: Mike Drob
>
> When needing to change a tserver parameter (e.g. java heap space) across the entire cluster, there is not a graceful way to perform a rolling restart.
> The naive approach of just killing tservers one at a time causes a lot of churn on the cluster as tablets move around and zookeeper tries to maintain current state.
> Potential solutions might be via a fancy fate operation, with coordination by the master. Ideally, the master would know which servers are 'safe' to restart and could minimize overall impact during the operation.



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