Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-8276

LazyPersistFileScrubber should be disabled if scrubber interval configured zero

    Details

    • 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
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      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)
      

        Attachments

        1. HDFS-8276_1.patch
          6 kB
          Surendra Singh Lilhore
        2. HDFS-8276.patch
          2 kB
          Surendra Singh Lilhore

          Issue Links

            Activity

              People

              • Assignee:
                surendrasingh Surendra Singh Lilhore
                Reporter:
                surendrasingh Surendra Singh Lilhore
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: