[
https://issues.apache.org/jira/browse/HDDS-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885464#comment-17885464
]
Ethan Rose commented on HDDS-11481:
-----------------------------------
Hi [~slfan1989] thanks for looking into this. The more detailed information you
have listed here and the screenshot shared seem like things that would be
better suited for Recon. Component web UIs are useful for seeing things
specific to that component, for example if it sees the same set of config keys
and Ratis leader as the others. For the items you listed here, I think Recon
has a lot of this already and it's probably best not to split our development
efforts between components. Recon has also been receiving UI improvements under
HDDS-11153 as well. Feel free to contribute more functionality to Recon if you
think it will be helpful. See also HDDS-11341. A lot of observability goals can
be accomplished by adding/improving metrics and building Grafana dashboards to
keep in the Ozone repo.
bq. 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.
Rather than for completeness, what is the use case for this feature? In what
scenario would we want the datanode process running but not registered or
reporting to SCM?
> 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]
