[
https://issues.apache.org/jira/browse/HDFS-16521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HDFS-16521:
--------------------------------
Description:
Providing DFS API to retrieve slow nodes would 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.
The other purpose of such API is for HDFS downstreamers without direct access
to namenode http port (only rpc port accessible) to retrieve slownodes.
was:
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.
> 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: 2h 40m
> Remaining Estimate: 0h
>
> Providing DFS API to retrieve slow nodes would 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.
> The other purpose of such API is for HDFS downstreamers without direct access
> to namenode http port (only rpc port accessible) to retrieve slownodes.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
