[ 
https://issues.apache.org/jira/browse/HDFS-16678?focusedWorklogId=794584&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-794584
 ]

ASF GitHub Bot logged work on HDFS-16678:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Jul/22 01:50
            Start Date: 24/Jul/22 01:50
    Worklog Time Spent: 10m 
      Work Description: ZanderXu commented on PR #4606:
URL: https://github.com/apache/hadoop/pull/4606#issuecomment-1193226247

   @goiri Sir, I have updated the patch and added some UTs, please help me 
review it again. Thanks




Issue Time Tracking
-------------------

    Worklog Id:     (was: 794584)
    Time Spent: 1h  (was: 50m)

> RBF supports disable getNodeUsage() in RBFMetrics
> -------------------------------------------------
>
>                 Key: HDFS-16678
>                 URL: https://issues.apache.org/jira/browse/HDFS-16678
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: ZanderXu
>            Assignee: ZanderXu
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> In our prod environment, we try to collect RBF metrics every 15s through 
> jmx_exporter. And we found that collection task often failed. 
> After tracing and found that the collection task is blocked at getNodeUsage() 
> in RBFMetrics, because it will collection all datanode's usage from 
> downstream nameservices.  This is a very expensive and almost useless 
> operation. Because in most scenarios, each NameSerivce contains almost the 
> same DNs. We can get the data usage's from any one nameservices, not from RBF.
> So I feel that RBF should supports disable getNodeUsage() in RBFMetrics.



--
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