[
https://issues.apache.org/jira/browse/HDFS-14703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213932#comment-17213932
]
Hemanth Boyina commented on HDFS-14703:
---------------------------------------
thanks [~shv] for your work
gone through the design doc , it was great , i have some questions
1) It is clear that on startup we decide the number of partitions based on
number of inodes in the image , but how do we decide range of RangeGsets on a
first time installation of cluster ?
2)
{quote}locking schema would be to allow Latch Lock for some operations combined
with the Global Lock for the other ones
{quote}
for operations like mkdir some times it is required to acquire locks of
different RangeGSets ,In the case of Recursive Mkdir we might need to acquire
locks of different RangeGSets , if some of the RangeGsets are locked for other
operations then the Range Map lock might have to wait for long time
3)
{quote}I attached two remaining patches 003 and 004 that should apply to
current trunk.
{quote}
are these patches should be applied on top of 003 and 004 in
[^001-partitioned-inodeMap-POC.tar.gz] ? looks some files were missing in
patches of [^002-partitioned-inodeMap-POC.tar.gz]
> 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,
> 002-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]
