[
https://issues.apache.org/jira/browse/HDDS-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886541#comment-17886541
]
Shilun Fan commented on HDDS-11481:
-----------------------------------
Thank you very much for your message！your suggestion is excellent. I agree that
we should avoid making the SCM more complex.
Regarding Option 1 that you mentioned, after giving it more thought, creating
an additional configuration file may not be the best choice either, as it would
add extra overhead for us. I found that we persist all DN lists in the
Pipeline. However, due to the nature of the Pipeline, we can only store active
DNs. I think we can make some small adjustments in the `DataNodeSafeModeRule`
to output unregistered DNs in verbose mode.
If you have time, please take a look at HDDS-11243: SCM SafeModeRule Support EC
(#7008). I have improved the `DataNodeSafeModeRule` to make it more reliable,
and I believe it can output more detailed information.
As for Option 2, I would like to contribute to that. In our internal system, we
widely use Grafana, and I will configure a new panel to better display DN
information. Once we complete this panel, I would appreciate your help in
reviewing it. Thanks again!
> 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]
