You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Hui Fei (Jira)" <ji...@apache.org> on 2026/06/09 04:27:01 UTC
[jira] [Updated] (HDDS-1953) Remove pipeline persistent in SCM
[ https://issues.apache.org/jira/browse/HDDS-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hui Fei updated HDDS-1953:
--------------------------
Target Version/s: 2.3.0 (was: 2.2.0)
<<Bulk update>>
Apache Ozone 2.2.0 release is in progress. I'm updating all unresolved jiras targeting 2.2.0 to retarget 2.3.0.
> Remove pipeline persistent in SCM
> ---------------------------------
>
> Key: HDDS-1953
> URL: https://issues.apache.org/jira/browse/HDDS-1953
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Reporter: Sammi Chen
> Assignee: Sammi Chen
> Priority: Major
> Labels: TriagePending
>
> Currently, SCM will persistent pipeline in metastore with datanode information locally. After SCM restart, it will reload all the pipelines from the metastore. If there is any datanode information change during the whole SCMc lifecycle, the persisted pipeline is not updated.
--
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