Uploaded image for project: 'Accumulo'
  1. Accumulo
  2. ACCUMULO-802 table namespaces
  3. ACCUMULO-2084

Potential deadlock with namespace reservations in clone table fate operation

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Invalid
    • None
    • None
    • client, master, tserver
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ctubbsii Christopher Tubbs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: