You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/12/21 08:32:00 UTC
[jira] [Commented] (HDDS-3696) Multiple SCMs manage each datanode set for one OM
[ https://issues.apache.org/jira/browse/HDDS-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650320#comment-17650320 ]
mingchao zhao commented on HDDS-3696:
-------------------------------------
Ozone 1.3.0 had been released and we currently have more than 600 open issues targeted for 1.3.0. I am moving the target field to 1.4.0.
If there is anything needs to be discussed about the Target Version, Please reach out to me via Apache email or Slack.
> Multiple SCMs manage each datanode set for one OM
> -------------------------------------------------
>
> Key: HDDS-3696
> URL: https://issues.apache.org/jira/browse/HDDS-3696
> Project: Apache Ozone
> Issue Type: New Feature
> Components: Ozone Manager
> Reporter: Baolong Mao
> Priority: Major
> Attachments: screenshot-1.png
>
>
> As Anu Engineer referenced at DataWorks Summit, if there are huge data, SCM can be separate to multiply SCMs.
> https://www.youtube.com/watch?v=WvEu6d76EIw
> In our scenario, our purpose is using multi-SCMs to manage different datanode group, each SCM can have different type or replication-factor pipeline. OM can get the right related SCM of a key through the key-group map information. We can also transfer files from a scm to another one with the data moving together.
> !screenshot-1.png!
--
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