You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:40:07 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 ]

Ethan Rose updated HDDS-1953:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> 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.3.4#803005)

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