[
https://issues.apache.org/jira/browse/HDFS-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031938#comment-18031938
]
ASF GitHub Bot commented on HDFS-16993:
---------------------------------------
github-actions[bot] commented on PR #5597:
URL: https://github.com/apache/hadoop/pull/5597#issuecomment-3430009135
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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]
