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 "lei w (Jira)" <ji...@apache.org> on 2023/12/11 13:31:00 UTC

[jira] [Resolved] (HDFS-16020) DatanodeReportType should add LIVE_NOT_DECOMMISSIONING type

     [ https://issues.apache.org/jira/browse/HDFS-16020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

lei w resolved HDFS-16020.
--------------------------
    Resolution: Invalid

> DatanodeReportType should add LIVE_NOT_DECOMMISSIONING type
> -----------------------------------------------------------
>
>                 Key: HDFS-16020
>                 URL: https://issues.apache.org/jira/browse/HDFS-16020
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: balancer &amp; mover, namanode
>            Reporter: lei w
>            Assignee: lei w
>            Priority: Minor
>         Attachments: HDFS-16020.001.patch
>
>
> Balancer builds cluster nodes by getDatanodeStorageReport(DatanodeReportType.LIVE) method。If the user does not specify the exclude node list, the balancer may migrate data to the DataNode in the decommission state. Should we filter out nodes in the decommission state by a new DatanodeReportType(LIVE_NOT_DECOMMISSIONING) regardless of whether the user specifies the exclude node list ?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org