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

BlockInvalidateLimit value is incorrectly set after namenode heartbeat interval reconfigured

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.9.0, 3.0.0-beta1
    • Component/s: hdfs, namenode
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      HDFS-1477 provides an option to reconfigured namenode heartbeat interval without restarting the namenode. When the heartbeat interval is reconfigured, blockInvalidateLimit gets recounted

       this.blockInvalidateLimit = Math.max(20 * (int) (intervalSeconds),
              DFSConfigKeys.DFS_BLOCK_INVALIDATE_LIMIT_DEFAULT);
      

      this doesn't honor the existing value set by dfs.block.invalidate.limit.

        Attachments

        1. HDFS-12082.004.patch
          5 kB
          Weiwei Yang
        2. HDFS-12082.003.patch
          5 kB
          Weiwei Yang
        3. HDFS-12082.002.patch
          4 kB
          Weiwei Yang
        4. HDFS-12082.001.patch
          4 kB
          Weiwei Yang

          Issue Links

            Activity

              People

              • Assignee:
                cheersyang Weiwei Yang
                Reporter:
                cheersyang Weiwei Yang
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: