[
https://issues.apache.org/jira/browse/ACCUMULO-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs updated ACCUMULO-2084:
----------------------------------------
Assignee: (was: Christopher Tubbs)
> 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
> 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.2#6252)
