Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.3.6
-
None
-
None
-
Version: 3.3.6
Location: hadoop/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/HeartbeatManager.java, in <init> method, lines 83-144.
Description
When initializing the HeartbeatManager, if the configuration parameter dfs.namenode.heartbeat.recheck-interval is greater than dfs.namenode.stale.datanode.interval, the heartbeat recheck interval is adjusted to match the stale datanode interval. However, the original implementation only logs a message when this adjustment occurs, leaving other configurations without any feedback, even when the parameters are not properly aligned. This can lead to a lack of transparency and understanding for the end-users who might be unaware of the parameter relationship or have misconfigured values.
Expected Behavior:
The system should log detailed information about the relationships between configuration parameters, especially when their values do not align with the expected behavior. This will help users ensure that the configurations are set correctly.
How-to-Fix: We propose adding enhanced logging to clearly expose the relationships between the configuration parameters. This will ensure users are informed about the implications of their settings.