You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "István Fajth (Jira)" <ji...@apache.org> on 2023/11/20 22:07:00 UTC

[jira] [Created] (HDDS-9733) DatanodeDetails should only contain those ports the DN actually listens to

István Fajth created HDDS-9733:
----------------------------------

             Summary: DatanodeDetails should only contain those ports the DN actually listens to
                 Key: HDDS-9733
                 URL: https://issues.apache.org/jira/browse/HDDS-9733
             Project: Apache Ozone
          Issue Type: Improvement
            Reporter: István Fajth
            Assignee: István Fajth


Currently the port list in DatanodeDetails is built up based on configuration, and based on the datanode.id file. If ever a port was saved to the datanode.id, it will be part of the DatanodeDetails object, even if configuration does not allow the existence of that port.

This is a problem with HTTP and HTTPS ports, that are also used to render Datanode WebUI links on the SCM's WebUI for example.
As DNs never remove these ports from the port list (because old values are read from datanode.id file), it is impossible to tell if a DN listens on HTTP or HTTPS port or in some cases both.

It would be nice to list only the active ports of the Datanode instead of all possibilities we know about, as atm there can be cases, where the DN has HTTPS_ONLY as the ozone.http.policy, while listing HTTP and HTTPS ports in the DatanodeDetails. I have not checked, but it might be that the port value can also contain an obsolete number from an old config, if it is not used in the current config.



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

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