LoggingResearch created HDFS-17612:
--------------------------------------
Summary: Expose Configuration Parameter Relationships in
HeartbeatManager
Key: HDFS-17612
URL: https://issues.apache.org/jira/browse/HDFS-17612
Project: Hadoop HDFS
Issue Type: Improvement
Components: hdfs
Affects Versions: 3.3.6
Environment: 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.
Reporter: LoggingResearch
Attachments: TestHeartbeatHandling.java, original-vs-log-enhanced.md
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
