You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@asterixdb.apache.org by "Ritik Raj (Jira)" <ji...@apache.org> on 2025/03/11 07:24:00 UTC

[jira] [Assigned] (ASTERIXDB-3574) Enhance concurrency in DatasetLifecycleManager by replacing the global lock with resource-specific locks where applicable.

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

Ritik Raj reassigned ASTERIXDB-3574:
------------------------------------

    Assignee: Ritik Raj

> 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
>             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)