[
https://issues.apache.org/jira/browse/HDFS-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-8276:
--------------------------------
Resolution: Fixed
Fix Version/s: 2.8.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Verified that the test failure is unrelated to your patch. Also ignoring the
checkstyle warning for now pending resolution of checkstyle issues.
Committed for 2.8. Thank you for the contribution [~surendrasingh].
> 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
> Fix For: 2.8.0
>
> Attachments: HDFS-8276.patch, HDFS-8276_1.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
(v6.3.4#6332)
