Layered table lock potentially not being held long enough

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Layered Tables
    • Storage Engines, Storage Engines - Transactions
    • None
    • None

      While draining ingest tables, we take the layered table lock while getting the number of open tables. However, it's possible that the list of entries could get reallocated, or that individual entries could be removed after we release the lock.

      There's a big performance penalty for holding the lock while doing the copy, so we should be really careful about choosing to hold the lock for longer.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Will Korteland
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: