[
https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703943#comment-14703943
]
Hadoop QA commented on HDFS-6244:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12751344/HDFS-6244.v6.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 4e14f79 |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/12050/console |
This message was automatically generated.
> 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, HDFS-6244.v6.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)
