[
https://issues.apache.org/jira/browse/HDFS-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032095#comment-17032095
]
Ayush Saxena commented on HDFS-14703:
-------------------------------------
Thanx [~shv] for the design, Overall design seems interesting.
One doubt :
{quote} For general case renames, which include moving a large directory ubder
another parent, could require locking multiple partitions. In the worst case it
could be equivalent (in performance) to holding a global lock
{quote}
As you said in case of renames it may require locking up multiple partitions,
In case of heavy loads, is it possible that a rename call may get stuck as it
isn't able to grab the locks on multiple partitions at one time? One of the
partition being alternatively always held?
> NameNode Fine-Grained Locking via Metadata Partitioning
> -------------------------------------------------------
>
> Key: HDFS-14703
> URL: https://issues.apache.org/jira/browse/HDFS-14703
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs, namenode
> Reporter: Konstantin Shvachko
> Priority: Major
> Attachments: 001-partitioned-inodeMap-POC.tar.gz, NameNode
> Fine-Grained Locking.pdf, NameNode Fine-Grained Locking.pdf
>
>
> We target to enable fine-grained locking by splitting the in-memory namespace
> into multiple partitions each having a separate lock. Intended to improve
> performance of NameNode write operations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
