asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abdullah Alamoudi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ASTERIXDB-2012) LSMBTreeRangeSearchCursor unlocks twice in some cases
Date Thu, 03 Aug 2017 07:19:00 GMT

     [ https://issues.apache.org/jira/browse/ASTERIXDB-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abdullah Alamoudi updated ASTERIXDB-2012:
-----------------------------------------
    Component/s: TX - Transactions

> LSMBTreeRangeSearchCursor unlocks twice in some cases
> -----------------------------------------------------
>
>                 Key: ASTERIXDB-2012
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2012
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: TX - Transactions
>            Reporter: Abdullah Alamoudi
>            Assignee: Abdullah Alamoudi
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message