Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 12 Jan 2015 17:24:34 +0000 (UTC)
From: "Denis Petrov (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12766890.1421083062000.61624.1421083474462@Atlassian.JIRA>
In-Reply-To: <JIRA.12766890.1421083062000@Atlassian.JIRA>
References: <JIRA.12766890.1421083062000@Atlassian.JIRA>
 <JIRA.12766890.1421083062303@arcas>
Subject: [jira] [Commented] (ACCUMULO-3471) Adding a new tserver puts some
 tables offline for few minutes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273801#comment-14273801 ] 

Denis Petrov commented on ACCUMULO-3471:
----------------------------------------

Killing all the tservers and start cluster is perhaps faster than add a single server.

> Adding a new tserver puts some tables offline for few minutes
> -------------------------------------------------------------
>
>                 Key: ACCUMULO-3471
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3471
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.6.1
>         Environment: Ubuntu 12.04
>            Reporter: Denis Petrov
>
> I run an Accumulo cluster with 15 tservers with about 6000 tablets on each (disks are quite slow - each node has 2*4Tb SATA)
> When a new tserver added to the cluster, the rebalancing procedure starts.
> During this procedure some tablets are offline and unreachable during 5-10 minutes.
> It is visible in http://monitor:50095/tables and by timeouts on client side.
> The rebalancing caused by killing a tserver converges much faster then rebalancing caused by adding a tserver.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)