[HDFS-12082] BlockInvalidateLimit value is incorrectly set after namenode heartbeat interval reconfigured

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-beta1
• Component/s: hdfs, namenode
• Hadoop Flags: Reviewed
• Assignee: Weiwei Yang
• Reporter: Weiwei Yang
• Created: 04/Jul/17 10:10
• Updated: 01/Aug/17 06:41
• Resolved: 31/Jul/17 18:36

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.

Issue Links

• is related to: HDFS-1477 Support reconfiguring dfs.heartbeat.interval and dfs.namenode.heartbeat.recheck-interval without NN restart