[
https://issues.apache.org/jira/browse/HDDS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057818#comment-17057818
]
Marton Elek commented on HDDS-3167:
-----------------------------------
How would you like to decide the replication factor for a specific container?
Do you suggest to use one global settings or some kind of per-container
settings?
As a first step a generic settings seems to be enough, but what if somebody
change the settings and restart the SCM. Should it be applied for all the
remaining containers?
If we would like to support EC in the future it would be great to support
per-container replication settings. In fact, we need pairs of settings. For
example:
RATIS/THREE (when it's open) --> THREE (when it's closed)
RATIS/ONE (when it's open) --> EC-5-2 (when it's closed)
One approach to support this is introducing a the "storage class", similar to
the S3 storage class.
For example
REDUCED = RATIS/ONE (for open) and THREE (for closed))
STANDARD = RATIS/THREE (open) and TWO (closed)
INFREQUENT = RATIS/THREE (open) and EC (closed)
It's not strictly about this issue, just thinking loudly here.
> Support different replication factor for CLOSED Container
> ---------------------------------------------------------
>
> Key: HDDS-3167
> URL: https://issues.apache.org/jira/browse/HDDS-3167
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Sammi Chen
> Priority: Major
>
> For open container, it's replication is decided by Ratis pipeline number
> number. For closed container, this is no such constrain. We can support more
> replication factor cases, such as 2 factor, to save storage for some cold
> data.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
