[jira] [Updated] (HDFS-17384) HDFS NameNode Fine-Grained Locking Phase I

["ZanderXu (Jira)" <ji...@apache.org>]

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

ZanderXu updated HDFS-17384:
----------------------------
    Component/s: namenode

> HDFS NameNode Fine-Grained Locking Phase I
> ------------------------------------------
>
>                 Key: HDFS-17384
>                 URL: https://issues.apache.org/jira/browse/HDFS-17384
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: ZanderXu
>            Assignee: ZanderXu
>            Priority: Major
>              Labels: FGL, pull-request-available
>
> First, we can replace the current global lock with two locks, global FS lock and global BM lock.
> The global FS lock is used to make directory tree-related operations thread-safe.
> The global BM lock is used to make block-related operations and DN-related operations thread-safe.
>  
> For some operations involving both directory tree and block or DN, the global FS lock and the global BM lock are acquired.
>  
> The lock order should be:
>  * The global FS lock
>  * The global BM lock
>  
> There are some special requirements for this ticket.
>  * End-user can choose to use global lock or fine-grained lock through configuration.
>  * Try not to modify the current implementation logic as much as possible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org