elek commented on pull request #1208: URL: https://github.com/apache/hadoop-ozone/pull/1208#issuecomment-681922380
> Dynamic model seems a good way, so this storage class will bee a user-defined storage class, right? And then, we should persist storage class info (factor/type) into db and admin user can update the storage class info via CLI command way. As a first step I would be happy to make it configurable (instead of having the config build time) and admin can update the config and restart the cluster. But yes, later it can be more and more dynamic (like storing it and providing CLI) This patch is mainly about the framework. If we have storage class as an abstraction level we can add more and more configuration options: for example the storage format on the datanode, erasure coding parameters. Or we can create an experimental, different write path without changing the existing code. Storage-class abstraction can help to separate the configuration from the user interface. User can choose from understandable storage class names and admin can (re)configure the details in the background. ---------------------------------------------------------------- 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: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
