Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 28 Feb 2014 18:14:19 +0000 (UTC)
From: "Bill Havanki (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12697816.1393540339914.126078.1393611259642@arcas>
In-Reply-To: <JIRA.12697816.1393540339914@arcas>
References: <JIRA.12697816.1393540339914@arcas>
Subject: [jira] [Reopened] (ACCUMULO-2422) Backup master can miss acquiring
 lock when primary exits
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bill Havanki reopened ACCUMULO-2422:
------------------------------------


I think Eric's fix should be fine, but I want to do more testing, and possibly add some logging and refinement.

> Backup master can miss acquiring lock when primary exits
> --------------------------------------------------------
>
>                 Key: ACCUMULO-2422
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2422
>             Project: Accumulo
>          Issue Type: Bug
>          Components: fate, master
>    Affects Versions: 1.5.1
>            Reporter: Bill Havanki
>            Assignee: Bill Havanki
>            Priority: Critical
>              Labels: failover, locking
>             Fix For: 1.6.0, 1.5.2
>
>
> While running randomwalk tests with agitation for the 1.5.1 release, I've seen situations where a backup master that is eligible to grab the master lock continues to wait. When this condition arises and the other master restarts, both wait for the lock without success.
> I cannot reproduce the problem reliably, and I think more investigation is needed to see what circumstances could be causing the problem.


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