[HDFS-8276] LazyPersistFileScrubber should be disabled if scrubber interval configured zero

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: namenode
• Hadoop Flags: Reviewed
• Assignee: Surendra Singh Lilhore
• Reporter: Surendra Singh Lilhore
• Created: 28/Apr/15 10:11
• Updated: 30/Aug/16 01:35
• Resolved: 01/May/15 18:18

Description

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, scrubber should be disable if dfs.namenode.lazypersist.file.scrub.interval.sec is zero.

Currently namenode startup is failing if interval configured zero

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)

Issue Links

• relates to: HDFS-6929 NN periodically unlinks lazy persist files with missing replicas from namespace