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

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

                Author: ASF GitHub Bot
            Created on: 31/Mar/22 06:06
            Start Date: 31/Mar/22 06:06
    Worklog Time Spent: 10m 
      Work Description: jojochuang commented on pull request #4107:
URL: https://github.com/apache/hadoop/pull/4107#issuecomment-1084132385


   I've wanted to build a UI to expose the slow datanode metrics more easily. 
For example at the NameNode itself or in Cloudera Manager Chart System. Never 
got the time to make one.
   
   But the biggest complaint from the users was that it is disabled by default 
and it's annoying to restart the cluster just to refresh the configuration and 
wait for the slow node to show up again. It would be much more useful it can be 
made available on demand at runtime.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 750775)
    Time Spent: 1h 40m  (was: 1.5h)

> DFS API to retrieve slow datanodes
> ----------------------------------
>
>                 Key: HDFS-16521
>                 URL: https://issues.apache.org/jira/browse/HDFS-16521
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> In order to build some automation around slow datanodes that regularly show 
> up in the slow peer tracking report, e.g. decommission such nodes and queue 
> them up for external processing and add them back later to the cluster after 
> fixing issues etc, we should expose DFS API to retrieve all slow nodes at a 
> given time.
> Providing such API would also help add an additional option to "dfsadmin 
> -report" that lists slow datanodes info for operators to take a look, 
> specifically useful filter for larger clusters.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to