You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Mohammadhani Fouladgar (Jira)" <ji...@apache.org> on 2026/08/26 22:19:00 UTC
[jira] [Assigned] (HDDS-16300) Allow the Ozone Manager to dynamically reconfigure its SCM node list (ozone.scm.nodes / ozone.scm.address) without a restart
[ https://issues.apache.org/jira/browse/HDDS-16300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mohammadhani Fouladgar reassigned HDDS-16300:
---------------------------------------------
Assignee: Mohammadhani Fouladgar
> Allow the Ozone Manager to dynamically reconfigure its SCM node list (ozone.scm.nodes / ozone.scm.address) without a restart
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HDDS-16300
> URL: https://issues.apache.org/jira/browse/HDDS-16300
> Project: Apache Ozone
> Issue Type: New Feature
> Reporter: Mohammadhani Fouladgar
> Assignee: Mohammadhani Fouladgar
> Priority: Major
>
> HDDS-13890 made DataNodes refresh their SCM connections without a restart, but it only touched the DataNode heartbeat/registration path (SCMConnectionManager + StateContext endpoints). The OM reaches SCM through a different mechanism: the SCMFailoverProxyProvider family, which loads the SCM list once at startup via SCMNodeInfo.buildNodeInfo(conf) (SCMFailoverProxyProviderBase) and never reloads. The OM does not register ozone.scm.nodes as reconfigurable, and the proxy providers have no reload hook.
--
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