fapifta opened a new pull request #3262: URL: https://github.com/apache/ozone/pull/3262
## What changes were proposed in this pull request? The change introduces the OM and HDDS LayoutFeature for EC. In order for EC to work, there are no upgrade actions necessary so none are defined, EC does work based on the normal facilities, and solves the erasure coded storage of data solely on the client side. The server side just gets knowledge about the fact that data inside an object is erasure coded with the ReplicationConfig. The change also introduces a new ClientVersion to mark that the client side supports erasure coded storage, also fixes a few APIDoc typos where ClientVersion remained ClientVersions during the rename of the class. The change also adds request and response validation to ensure the following backward compatibility and upgrade related questions: - During an upgrade until the cluster is finalized, there aren't any way to create a key/bucket/container/pipeline with ECReplicationConfig. - After an upgrade a client is not served with any type of object that has an ECReplicationconfig that the old client would not understand. The change affects SCM and OM, so that SCM Admin and SCM Container Location requests are also disabled alongside with any requests that the OM ClientProtocol provides. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-5909 ## How was this patch tested? As the logic added is so simple, I did not added new tests for the request/response validation so far, current tests should work without any modification, while in order to add compatibility tests for the client and server side I believe we need a bigger effort to extend what we already have for compatibility alongside with the development related to HDDS-6390 -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
