[
https://issues.apache.org/jira/browse/HDDS-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302586#comment-17302586
]
Marton Elek commented on HDDS-4967:
-----------------------------------
Thanks the question [~Nicholas Niu]. It depends the definition of "possible" ;-)
Right now we have no such options, but it's possible to implement ;-)
The biggest problem is the containers are re-used. If you need any specific
container type, you should differentiate between the containers during the
allocation and each client should have all the required metadata and sent by
the first request.
EC branch has a proposal to use ReplicationConfig (HDDS-4882) which can use
additional metadata which can contains additional metadata (like the real
container implementation).
Not sure if I answered the question, let me know if you have more specific
question.
> Is it possible to support multiple containerTypes on the SCM side?
> ------------------------------------------------------------------
>
> Key: HDDS-4967
> URL: https://issues.apache.org/jira/browse/HDDS-4967
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Affects Versions: 1.1.0
> Reporter: GuoHao
> Priority: Minor
> Fix For: 1.1.0
>
>
> Is it possible to support multiple containerTypes on the SCM side?
> Now supports multiple containerTypes on the datanode side.
>
> Such as:
> 1. The datanode side implements a container optimized for storing small
> blocks
> 2. The scm side can match the container of the corresponding containerType
> for storage according to blocks of different sizes
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
