You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/12/04 13:13:50 UTC

[GitHub] [ozone] elek commented on pull request #1419: HDDS-3755. [DESIGN] Storage-class for Ozone

elek commented on pull request #1419:
URL: https://github.com/apache/ozone/pull/1419#issuecomment-738777079


   > It is not sufficient to just define the replication factor. The replication/recovery behavior completely changes based on the replication scheme. E.g. for EC, we are talking about picking some coordinator during recovery. How do you abstract away behavior like that?
   
   I am not sure If I understand this question. Offline-recovery and co-ordinator election is an internal implementation detail of EC replication scheme. The only role of storage-class is to *select* and *configure* the required configuration scheme. If EC 3:2 is configured we will have EC 3:2 containers created which will be managed by SCM as EC 3:2 containers.  


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



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