[
https://issues.apache.org/jira/browse/ASTERIXDB-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Maxon updated ASTERIXDB-3574:
---------------------------------
Labels: triaged (was: )
> Enhance concurrency in DatasetLifecycleManager by replacing the global lock
> with resource-specific locks where applicable.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: ASTERIXDB-3574
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3574
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: STO - Storage
> Affects Versions: 0.9.10
> Reporter: Ritik Raj
> Assignee: Ritik Raj
> Priority: Major
> Labels: triaged
> Fix For: 0.9.10
>
>
> Currently, all dataset and index metadata operations (create, register, open,
> close, and unregister) in DatasetLifecycleManager are synchronized using a
> global lock. This limits concurrency.
> To improve performance, the global lock can be *downgraded* to a
> resource-specific lock when operating on individual datasets or indexes. This
> will allow more concurrency while maintaining correctness.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
