You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/07 11:39:00 UTC
[jira] [Work logged] (HDFS-16581) Print node status when executing printTopology
[ https://issues.apache.org/jira/browse/HDFS-16581?focusedWorklogId=779003&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-779003 ]
ASF GitHub Bot logged work on HDFS-16581:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Jun/22 11:38
Start Date: 07/Jun/22 11:38
Worklog Time Spent: 10m
Work Description: jianghuazhu commented on PR #4321:
URL: https://github.com/apache/hadoop/pull/4321#issuecomment-1148550038
Thanks @tomscut .
Hi @jojochuang @aajisaka , can you help review this pr?
Thank you very much.
Issue Time Tracking
-------------------
Worklog Id: (was: 779003)
Time Spent: 1h 20m (was: 1h 10m)
> Print node status when executing printTopology
> ----------------------------------------------
>
> Key: HDFS-16581
> URL: https://issues.apache.org/jira/browse/HDFS-16581
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: dfsadmin, namenode
> Affects Versions: 3.3.0
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> We can use the dfsadmin tool to see which DataNodes the cluster has, and some of these nodes are alive, DECOMMISSIONED, or DECOMMISSION_INPROGRESS. It would be helpful if we could get this information in a timely manner, such as troubleshooting cluster failures, tracking node status, etc.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org