[
https://issues.apache.org/jira/browse/HDDS-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose updated HDDS-3696:
-----------------------------
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.
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]