[ 
https://issues.apache.org/jira/browse/HDDS-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siyao Meng updated HDDS-3915:
-----------------------------
    Description: 
Implementation something similar to HDFS's {{NameNode#startTrashEmptier}} on 
OzoneManager to enable automatic trash clean up.

Some thoughts:
1. Ozone doesn't support efficient directory renaming (not until HDDS-2939 is 
fully merged).
- Possible solution: Override {{TrashPolicyDefault}} by setting 
{{fs.trash.classname}} in {{core-site.xml}}. So we can move files under 
{{/.Trash/<timestamp_of_delete>/}} instead of {{/.Trash/Current/}} to avoid 
folder renaming during checkpointing.
  - But this {{fs.trash.classname}} might affect ALL other FileSystems if 
configured in {{core-site.xml}}.
    - If there a way to only apply the config to o3fs and ofs.

  was:
Implementation something similar to HDFS's {{NameNode#startTrashEmptier}} on 
OzoneManager to enable automatic trash clean up.

Some thoughts:
1. Ozone doesn't support efficient directory renaming (not until HDDS-2939 is 
fully merged).
- Possible solution: Override {{TrashPolicyDefault}} by setting 
{{fs.trash.classname}} in {{core-site.xml}}. So we can move files under 
{{/.Trash/<timestamp_of_delete>/}} instead of {{/.Trash/Current/}} to avoid 
folder renaming during checkpointing. - But this {{fs.trash.classname}} might 
affect ALL other FileSystems if configured in {{core-site.xml}}. - If there a 
way to only apply the config to o3fs and ofs.


> Simple trash emptier on OM
> --------------------------
>
>                 Key: HDDS-3915
>                 URL: https://issues.apache.org/jira/browse/HDDS-3915
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Manager
>            Reporter: Siyao Meng
>            Assignee: Siyao Meng
>            Priority: Major
>
> Implementation something similar to HDFS's {{NameNode#startTrashEmptier}} on 
> OzoneManager to enable automatic trash clean up.
> Some thoughts:
> 1. Ozone doesn't support efficient directory renaming (not until HDDS-2939 is 
> fully merged).
> - Possible solution: Override {{TrashPolicyDefault}} by setting 
> {{fs.trash.classname}} in {{core-site.xml}}. So we can move files under 
> {{/.Trash/<timestamp_of_delete>/}} instead of {{/.Trash/Current/}} to avoid 
> folder renaming during checkpointing.
>   - But this {{fs.trash.classname}} might affect ALL other FileSystems if 
> configured in {{core-site.xml}}.
>     - If there a way to only apply the config to o3fs and ofs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org

Reply via email to