[
https://issues.apache.org/jira/browse/HDDS-13806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031366#comment-18031366
]
Ivan Andika commented on HDDS-13806:
------------------------------------
[~sshenoy] Sounds good, this is what we implemented internally. We used a
configuration which contains patterns to check for trash. cc: [~XiChen]
> Files are moved to different trash root when deleted through s3a://
> -------------------------------------------------------------------
>
> Key: HDDS-13806
> URL: https://issues.apache.org/jira/browse/HDDS-13806
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Sammi Chen
> Priority: Major
>
> When trash is enabled and user deletes a Ozone file through s3a:// schema,
> the file will be moved to HDFS default trash root, instead of Ozone default
> trash root. Since the trash deletion thread in Ozone only checks Ozone
> default trash root, so these files deleted through s3a:// will never get a
> chance to be deleted.
> HDFS trash behaivor:
> * For unencrypted files, the HDFS trash root is typically located in the
> user's home directory under /user/<username>/.Trash, where deleted files are
> moved to /user/<username>/.Trash/Current/OriginalPath.
> * For encrypted files, the trash root is within the encryption zone's root
> directory at /EncryptionZoneRoot/.Trash, and files are moved to
> /EncryptionZoneRoot/.Trash/$USER/Current/OriginalPath. The trash can be
> accessed using hdfs dfs -ls /user/<username>/.Trash or by using a path
> prefixed with hdfs://
> Ozone trash behavior:
> In Apache Ozone, the default trash location for keys in a File System
> Optimized (FSO) bucket is within the bucket itself. The specific path
> is:/<volume>/<bucket>/.Trash/<user>, where deleted files are moved to
> /<volume>/<bucket>/.Trash/<user>/Current/OriginalPath
> The problem is found by [~chenxi]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
