[
https://issues.apache.org/jira/browse/HDFS-8493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597140#comment-14597140
]
Vinayakumar B commented on HDFS-8493:
-------------------------------------
bq. Though most of the time the fsd lock is acquired within the fsn lock.
BlockManager and LeaseManager only requires the fsn lock but not the fsd lock.
We're in the process of cleaning up the locks of both fsn and fsd locks. At the
end of the day the NN should be able to process block reports w/o blocking
requests to the namespace.
Okay.
bq. Following are the functions where it has done the resolution
fsd.resolvePath(pc, src, pathComponents); by acquiring only fsn lock and not
fsd lock. Could you please take a look at it.
Thanks [~rakeshr] for listing out those methods. Can you file a follow-up jira
to handle those?
> Consolidate truncate() related implementation in a single class
> ---------------------------------------------------------------
>
> Key: HDFS-8493
> URL: https://issues.apache.org/jira/browse/HDFS-8493
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Haohui Mai
> Assignee: Rakesh R
> Attachments: HDFS-8493-001.patch, HDFS-8493-002.patch,
> HDFS-8493-003.patch, HDFS-8493-004.patch, HDFS-8493-005.patch,
> HDFS-8493-006.patch, HDFS-8493-007.patch, HDFS-8493-007.patch
>
>
> This jira proposes to consolidate truncate() related methods into a single
> class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
