[
https://issues.apache.org/jira/browse/HDDS-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kaijie Chen updated HDDS-7328:
------------------------------
Fix Version/s: 1.3.0
> Improve Deletion of FSO Paths
> -----------------------------
>
> Key: HDDS-7328
> URL: https://issues.apache.org/jira/browse/HDDS-7328
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Xu Shao Hong
> Assignee: Xu Shao Hong
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.3.0
>
>
> Currently, the deleting speed of paths in the FSO bucket is too slow.
> Every time the DirectoryDeletingService executes(every 1m by default), it
> chooses only one path from DeletedDirectroyTable and tries adding its
> sub-files and sub-dirs into the PurgeDirectories Request. The real deletion
> happens in OMKeyDeleteResponseWithFSO, which moved all sub-dirs into
> DeletedDirectroyTable. Then these sub-dirs will be chosen by the future
> execution of DirectoryDeletingService.
> In the real production environment, such deletion speed is not applicable.
> There could be lots of dirs deleted without sub-dirs or sub-files. The dir
> deletion speed would lag behind the dir creation speed.
> I propose to optimize the logic of the DirectoryDeletingService, we could
> consume all the quota (ozone.path.deleting.limit.per.task) to delete paths as
> much as possible. The good news is the PB is already designed to do so, we
> could add more PurgePathRequest in one PurgeDirectoriesRequest.
> -----------------------------------
> This should be compatible with HDDS-5048.
> This aims to improve the efficiency of the deletion if not enough sub-files
> or sub-dirs are chosen.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
