Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.4.0
-
Reviewed
Description
The logic of Reconfigure slow peer enable for Namenode requires the following optimizations:
1.Make SlowPeerTracker slowPeerTracker volatile.
2.When starting the NameNode, if the parameter dfs.datanode.peer.stats.enabled is set to false, DatanodeManager#startSlowPeerCollector() will not call, as a result the Slow peers collection thread 'slowPeerCollectorDaemon' will not be started .
If the parameter dfs.datanode.peer.stats.enabled is dynamically refreshed to true, the current logic will not call DatanodeManager#startSlowPeerCollector(), which to thread 'slowPeerCollectorDaemon' not started as expected, so we will optimize here
Attachments
Issue Links
- is related to
-
HDFS-16528 Reconfigure slow peer enable for Namenode
-
- Resolved
-
- links to