You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/02 09:36:00 UTC
[jira] [Work logged] (HDFS-16208) [FGL] Implement Delete API with FGL
[ https://issues.apache.org/jira/browse/HDFS-16208?focusedWorklogId=777369&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-777369 ]
ASF GitHub Bot logged work on HDFS-16208:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Jun/22 09:35
Start Date: 02/Jun/22 09:35
Worklog Time Spent: 10m
Work Description: jianghuazhu commented on PR #3376:
URL: https://github.com/apache/hadoop/pull/3376#issuecomment-1144654653
Hi @prasad-acit , nice to talk to you.
For delete using FGL, it may be safer to add child locks before fsn.removeLeasesAndINodes().
The reason here is that after finishing running unprotectedDelete(), there are still updated content, such as block-related updates, and snapshotManager deletes Snapshottable.
Before this, this was done while holding the FSNamesystemLock.
Based on the premise of safety, I make my proposal.
If my suggestion is wrong, please ignore it.
Issue Time Tracking
-------------------
Worklog Id: (was: 777369)
Time Spent: 40m (was: 0.5h)
> [FGL] Implement Delete API with FGL
> -----------------------------------
>
> Key: HDFS-16208
> URL: https://issues.apache.org/jira/browse/HDFS-16208
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Renukaprasad C
> Assignee: Renukaprasad C
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Replace all global locks for file / directory deletion with FGL.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org