accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-2084) Potential deadlock with namespace reservations in clone table fate operation
Date Mon, 23 Dec 2013 21:01:50 GMT
Christopher Tubbs created ACCUMULO-2084:
-------------------------------------------

             Summary: 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
            Reporter: Christopher Tubbs
            Assignee: Christopher Tubbs
             Fix For: 1.6.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)

Mime
View raw message