[
https://issues.apache.org/jira/browse/HDFS-8493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595735#comment-14595735
]
Vinayakumar B commented on HDFS-8493:
-------------------------------------
bq. The resolution should be in the lock of FSDirectory.
IMO, I think this is okay, especially for write ops, provided fsn writelock is
held. And I can see many places where this resolution is done under fsn lock
held, but not fsd lock.
This triggered thoughts, Why two separate locks, fsdir lock and fsnamesystem
locks.? Almost all ops are go through fsn with lock (read/write) held, and then
go on-to get fsdir locks.
Any thoughts?
> 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)
