[ 
https://issues.apache.org/jira/browse/HDDS-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886718#comment-17886718
 ] 

Ethan Rose commented on HDDS-11481:
-----------------------------------

Thanks. I filed HDDS-11525 to create a cluster membership dashboard.

> Enhanced SCM Support for DataNode Management
> --------------------------------------------
>
>                 Key: HDDS-11481
>                 URL: https://issues.apache.org/jira/browse/HDDS-11481
>             Project: Apache Ozone
>          Issue Type: Wish
>          Components: SCM
>            Reporter: Shilun Fan
>            Assignee: Shilun Fan
>            Priority: Major
>         Attachments: screenshot-1.png
>
>
> I plan to enhance SCM's support for DataNode management, including features 
> like blacklist and whitelist.
> Compared to the DataNode management functionality in HDFS, SCM's DataNode 
> management still has some incomplete features:
> 1. For instance, the blacklist and whitelist functionality is missing. 
> Currently, all DataNodes can register with SCM once they are started, but for 
> the sake of completeness, we should implement a blacklist feature.
> 2. The display list function for DataNodes in SCM is not user-friendly, with 
> the following issues: 
> -The list does not support global sorting. 
> - It cannot display the decommissioning progress. Once the decommissioning 
> process begins, we can only passively refresh the page or rely on metrics to 
> make judgments. 
> - Key information about DataNodes is missing from the list, such as the 
> number of containers and the number of pipelines.
> 3. In HDFS, if multiple DataNode versions are detected in the cluster, there 
> are helpful prompts, but SCM's recognition and support for multiple DataNode 
> versions are insufficient.



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

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

Reply via email to