hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siqi Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
Date Mon, 17 Aug 2015 20:52:46 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700204#comment-14700204
] 

Siqi Li commented on HDFS-6244:
-------------------------------

I think Ming is talking about cloning the conf instead of reading the namespace specific property.
Because for trash object, it should not be aware the concept of namespace. Also, I have tried
to create a constructor for trash to take namespace as a parameter. However, this namespace
also needs to pass to TrashPolicyDefault and Emptier, in order for them to read the namespace
specific property. Which makes a lot of changes. Therefore, I think passing a clone conf is
a cleaner approach.

> Make Trash Interval configurable for each of the namespaces
> -----------------------------------------------------------
>
>                 Key: HDFS-6244
>                 URL: https://issues.apache.org/jira/browse/HDFS-6244
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 2.0.5-alpha
>            Reporter: Siqi Li
>            Assignee: Siqi Li
>              Labels: BB2015-05-TBR
>         Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, HDFS-6244.v3.patch, HDFS-6244.v4.patch,
HDFS-6244.v5.patch
>
>
> Somehow we need to avoid the cluster filling up.
> One solution is to have a different trash policy per namespace. However, if we can simply
make the property configurable per namespace, then the same config can be rolled everywhere
and we'd be done. This seems simple enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message