[
https://issues.apache.org/jira/browse/ASTERIXDB-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351815#comment-16351815
]
ASF subversion and git services commented on ASTERIXDB-2270:
------------------------------------------------------------
Commit ad758c5258c5ed091b4270fd02f0693adf529ae3 in asterixdb's branch
refs/heads/master from [~alamoudi]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=ad758c5 ]
[ASTERIXDB-2270][STO] Fix Deadlock in LSMRTree
- user model changes: no
- storage format changes: no
- interface changes: no
details:
- The LSMRTreeWithAntiMatterTuplesSearchCursor was
using the includeMutableComponent incorrectly to
determine whether memory components are included.
- This change ensures that memory components cursors
are always closed and destroyed as part of the
cursor lifecycle.
- The change also includes a check that fails if a
virtual file was deleted and some of its pages
are still latched.
Validate pages of deleted vbc files are not latched
Change-Id: If91ac3a2fa9265f929867e0dc75bbe0b7fa0aed1
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2343
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mb...@apache.org>
> Deadlock on recycling of LSMRTree memory component
> --------------------------------------------------
>
> Key: ASTERIXDB-2270
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2270
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: STO - Storage
> Reporter: Abdullah Alamoudi
> Priority: Major
>
> In the build
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3222/console]
> The recycling of the memory component of the LSM R-Tree deadlocked because it
> pinned a free page and tried to get a write latch on it.
> However, a read latch that was acquired at some point was not released.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
