Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 3 Feb 2014 23:59:06 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12686203.1387832438529.30734.1391471946075@arcas>
In-Reply-To: <JIRA.12686203.1387832438529@arcas>
References: <JIRA.12686203.1387832438529@arcas>
Subject: [jira] [Updated] (ACCUMULO-2084) Potential deadlock with namespace
 reservations in clone table fate operation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

John Vines updated ACCUMULO-2084:
---------------------------------

    Fix Version/s:     (was: 1.6.0)
                   1.7.0

Non-issue while we only allow cloning within namespaces

> Potential deadlock with namespace reservations in clone table fate operation
> ----------------------------------------------------------------------------
>
>                 Key: ACCUMULO-2084
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2084
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client, master, tserver
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.7.0
>
>
> Clone table needs to reserve both the source and destination namespace, (as well as the source tableId) and it needs to do so in a predictable order, not attempting to grab the second until it gets the first... otherwise, deadlocks could occur. To ensure ordering, we need to make sure clone table (and other operations) reserve everything up front, reserving the namespaces first, and the tables second. The namespaces should be sorted before reserving, to ensure overlaps with other fate operations do not cause deadlocks.


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