You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2026/06/27 12:33:00 UTC
[jira] [Resolved] (HDDS-15682) Use the original configured host and port to identify SCM nodes
[ https://issues.apache.org/jira/browse/HDDS-15682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz-wo Sze resolved HDDS-15682.
-------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
The pull request is now merged.
> Use the original configured host and port to identify SCM nodes
> ---------------------------------------------------------------
>
> Key: HDDS-15682
> URL: https://issues.apache.org/jira/browse/HDDS-15682
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> The data structures such as SCMConnectionManager.scmMachines, StateContext.endpoint, etc. use InetSocketAddress to identify SCM nodes. Since the InetSocketAddress can changed in some environment such as Kubernetes, it is better to use the original configured host and port instead of the resolved InetSocketAddress.
--
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