arp7 commented on pull request #1973: URL: https://github.com/apache/ozone/pull/1973#issuecomment-801233001
> Can you please help with more specific, technical questions? Upgrades. Not just client->server compat, also downgrade concerns. E.g. if the new ReplicationConfig message is in the OM ratis log, will the old software fail after downgrades? Secondly if the new configuration introduces new functionality, we must ensure it is not used until upgrade is finalized. We either bring it through the upgrade framework or think of some other way. > After 4-5 month of discussion and sharing dozen of pages design docs, Was there a design note about these details of this index based approach? Perhaps I missed it. I am okay to have this be part of the jira description also. Will the clients send the old ReplicationFactor message in perpetuity? > I think sharing some initial POC code can help this discussion. It is very hard to tell from just the proto changes what direction we are going in. This is one instance in which a more complete patch with a short design note will help give reviewers a more complete picture. ---------------------------------------------------------------- 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]
