hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8276) LazyPersistFileScrubber should be disabled if scrubber interval configured zero
Date Thu, 30 Apr 2015 04:21:06 GMT

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

Arpit Agarwal commented on HDFS-8276:

Thanks for fixing this [~surendrasingh]. Just a nitpick, there should be spaces between the
{{else}} and the braces on line 1176. +1 with that fixed.

Also see if you want to add a unit test. It should be fairly simple.

> LazyPersistFileScrubber should be disabled if scrubber interval configured zero
> -------------------------------------------------------------------------------
>                 Key: HDFS-8276
>                 URL: https://issues.apache.org/jira/browse/HDFS-8276
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.6.0
>            Reporter: surendra singh lilhore
>            Assignee: surendra singh lilhore
>         Attachments: HDFS-8276.patch
> bq. but I think it is simple enough to change the meaning of the value so that zero means
'never scrub'. Let me post an updated patch.
> As discussed in [HDFS-6929|https://issues.apache.org/jira/browse/HDFS-6929], scrubber
should be disable if *dfs.namenode.lazypersist.file.scrub.interval.sec* is zero.
> Currently namenode startup is failing if interval configured zero
> {code}
> 2015-04-27 23:47:31,744 ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem
initialization failed.
> java.lang.IllegalArgumentException: dfs.namenode.lazypersist.file.scrub.interval.sec
must be non-zero.
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:828)
> {code}

This message was sent by Atlassian JIRA

View raw message