Uploaded image for project: 'Apache AsterixDB'
  1. Apache AsterixDB
  2. ASTERIXDB-2012

LSMBTreeRangeSearchCursor unlocks twice in some cases

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: TX - Transactions
    • Labels:
      None

      Description

      LSMBTreeRangeSearchCursor sometimes unlocks twice producing illegal state exception
      This happens if:
      1. the proceed call failed (causing instant lock to fail)
      2. the lock was acquired and then released. This happens if:
      a. the priority queue head was not coming from memory component.
      b. the priority queue head was from memory component and it didn't change when search was re-performed
      3. the tuple was found to be antimatter.

      Moreover, locks that are acquired in case the mutable component is not part of the search anymore are not released until the job completes.

        Attachments

          Activity

            People

            • Assignee:
              amoudi Abdullah Alamoudi
              Reporter:
              amoudi Abdullah Alamoudi
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: