[ 
https://issues.apache.org/jira/browse/HDFS-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796581#comment-17796581
 ] 

ASF GitHub Bot commented on HDFS-16993:
---------------------------------------

hfutatzhanghb commented on PR #5597:
URL: https://github.com/apache/hadoop/pull/5597#issuecomment-1855260225

   @ayushtkn @Hexiaoqiao @tomscut Hi, sir. I think we should better push this 
PR forward. Because it waste datanode's memory.  As the below screeshot show , 
it has 27K networkError key values!!!  
   
   <img width="838" alt="image" 
src="https://github.com/apache/hadoop/assets/25115709/d58f6421-ef70-4e45-9f93-ba51518bda31";>
   




> Datanode supports configure TopN DatanodeNetworkCounts
> ------------------------------------------------------
>
>                 Key: HDFS-16993
>                 URL: https://issues.apache.org/jira/browse/HDFS-16993
>             Project: Hadoop HDFS
>          Issue Type: Wish
>    Affects Versions: 3.3.5
>            Reporter: farmmamba
>            Priority: Major
>              Labels: pull-request-available
>
> In our prod environment, we try to collect datanode metrics every 15s through 
> jmx_exporter.  we found the datanodenetworkerror metric generates a lot.
> for example, if we have a cluster with 1000 datanodes, every datanode may 
> generate 999 datanodenetworkerror metrics, and overall datanodes will 
> generate 1000 multiple 999 = 999000 metrics. This is a very expensive 
> operation. In most scenarios, we only need the topN of it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to