Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 28 Dec 2013 18:27:50 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12633914.1361803568171.18554.1388255270428@arcas>
In-Reply-To: <JIRA.12633914.1361803568171@arcas>
References: <JIRA.12633914.1361803568171@arcas>
Subject: [jira] [Commented] (ACCUMULO-1088) master not balancing because
 balance information is out-of-date
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Newton commented on ACCUMULO-1088:
---------------------------------------

I have a vague recollection of a change that [~kturner] made for 1.5 that made this problem go away.  I've not chased it down to a particular commit, but it had something to do with re-establishing connections to tservers in the master whenever there was an IOException.

> master not balancing because balance information is out-of-date
> ---------------------------------------------------------------
>
>                 Key: ACCUMULO-1088
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1088
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.4.2
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>             Fix For: 1.5.0
>
>
> During tests with agitation, the test cluster would become unbalanced because the master did not realize a dead server was restarted.  All servers would be up, but the master would think that a dead server was still out there.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)