Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 10 Apr 2014 13:29:14 +0000 (UTC)
From: "Bill Havanki (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12706471.1396547768568.92789.1397136554577@arcas>
In-Reply-To: <JIRA.12706471.1396547768568@arcas>
References: <JIRA.12706471.1396547768568@arcas>
Subject: [jira] [Updated] (ACCUMULO-2621) Masters not restarting during
 concurrent randomwalk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Havanki updated ACCUMULO-2621:
-----------------------------------

    Fix Version/s:     (was: 1.6.1)
                       (was: 1.7.0)
                   1.6.0
         Assignee: Bill Havanki
           Status: Patch Available  (was: Open)

Review available. I'd like this in 1.6.0 if possible; it's minor, but includes information needed to ensure randomwalk succeeds.

> Masters not restarting during concurrent randomwalk
> ---------------------------------------------------
>
>                 Key: ACCUMULO-2621
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2621
>             Project: Accumulo
>          Issue Type: Test
>          Components: test
>            Reporter: Bill Havanki
>            Assignee: Bill Havanki
>            Priority: Critical
>              Labels: 16_qa_bug, randomwalk, test
>             Fix For: 1.6.0
>
>
> The Concurrent randomwalk test can stop and restart the masters. Under 1.6.0-SNAPSHOT, the stopped masters are not restarting, and eventually the test becomes stuck reporting "No matchers..." forever.
> Tested on 7-node CentOS 6.4 cluster, 2 masters. The active master seems to die first, then the standby that becomes the new master.


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