[
https://issues.apache.org/jira/browse/HDFS-17840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035789#comment-18035789
]
Srinivasu Majeti edited comment on HDFS-17840 at 11/6/25 10:13 AM:
-------------------------------------------------------------------
Hi [~szetszwo] /[~sodonnell] , Do we have any other related resolved issue
recently as we keep seeing it at times. This was recently observed post upgrade
from cloudera 7.1.6 to 7.1.7 SP3.
was (Author: smajeti):
Hi [~szetszwo] /[~sodonnell] , Do we have any other related resolved issue
recently as we keep seeing it at times.
> The "Nodes in Service" information is incorrect under DFS Storage Types in
> NameNode UI
> --------------------------------------------------------------------------------------
>
> Key: HDFS-17840
> URL: https://issues.apache.org/jira/browse/HDFS-17840
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.2.2
> Reporter: terrytlu
> Priority: Major
> Attachments: image-2025-09-23-11-34-26-420.png
>
>
> We found in our hadoop cluster, which has 26 nodes, while in NameNode UI,
> only show 3 nodes
> !image-2025-09-23-11-34-26-420.png|width=720,height=253!
> the problem still exists after merge
> https://issues.apache.org/jira/browse/HDFS-16402 ,this metric modification
> involves multiple data fields and heartbeat logic, it is difficult to
> guarantee atomicity.
>
> And the metrics are calculated using real-time increments and decrements,
> once it is corrupted, it cannot be restored. We recommend change the
> implementation to retrieve the data from
> org.apache.hadoop.hdfs.server.blockmanagement.DatanodeManager#datanodeMap to
> ensure that data is neither lost nor duplicated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
