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

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

                Author: ASF GitHub Bot
            Created on: 12/Jun/22 01:39
            Start Date: 12/Jun/22 01:39
    Worklog Time Spent: 10m 
      Work Description: virajjasani commented on PR #4321:
URL: https://github.com/apache/hadoop/pull/4321#issuecomment-1153041399

   > The change looks good to me.
   > 
   > I am a little worried that this will change the output structure of 
`printTopology`. I wonder if this will be an incompatible change. Do I need to 
add a releaseNote? @tasanuma @virajjasani Could you please give some 
suggestions? Thanks.
   
   @tomscut sounds good, we can keep this to trunk and add release note as well 
reg the output format change, thanks!




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

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

> 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 40m
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to