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 DAD1A11624 for ; Tue, 12 Aug 2014 15:13:12 +0000 (UTC) Received: (qmail 66685 invoked by uid 500); 12 Aug 2014 15:13:12 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 66638 invoked by uid 500); 12 Aug 2014 15:13:12 -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 66618 invoked by uid 99); 12 Aug 2014 15:13:12 -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 15:13:12 +0000 Date: Tue, 12 Aug 2014 15:13:12 +0000 (UTC) From: "Mike Drob (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: 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=14094145#comment-14094145 ] Mike Drob commented on ACCUMULO-1454: ------------------------------------- If we expose a user level command to request that a tablet be moved to a given destination, then external tools could implement their own rolling restarts. If any of those turn out to be really good in the general case (or even in the upgrade case), then we can always backport them. > 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)