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

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

ayushtkn commented on code in PR #5597:
URL: https://github.com/apache/hadoop/pull/5597#discussion_r1202191052


##########
hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml:
##########
@@ -6419,6 +6419,15 @@
       problem. In produce default set false, because it's have little 
performance loss.
     </description>
   </property>
+
+  <property>
+    <name>dfs.datanode.networkerrors.display.topcount</name>
+    <value>10</value>

Review Comment:
   by default it should be -1, and if it is -1 the behaviour should be like the 
previous one, like today





> 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