[ASTERIXDB-2012] LSMBTreeRangeSearchCursor unlocks twice in some cases

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: TX - Transactions
• Assignee: Abdullah Alamoudi
• Reporter: Abdullah Alamoudi
• Created: 03/Aug/17 07:17
• Updated: 08/Mar/18 04:52
• Resolved: 06/Sep/17 16:43

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.