...
There are no intermittent failures specific to the HDDS-2823 branch as of now. During the development , it was ensured all the CI checks are clean prior to every commit merge .The plan is to run repeated CI checks on the merge commit to master.
2. documentation
All the docs are available in the doc section DOCSInitial doc has been added by HDDS-4948.
3. design, attached the docs
All the design docs are also available in the doc section DOCSlinked from the documentation as part of HDDS-4948.
4. s3 compatibility
There are no incompatibilities with respect to s3. S3 is not changed at all (except that the OmUtils rename affected it)
5. support of containers / kubernetes:
Tested in Kubernetes and everythign everything worked well.
Example files are uploaded in the patch to: Jira
6. coverage/code quality:
...
9. third party dependencies/licence changes:
Checking the content of the two branches (find -type f | sort > ... + diff) the only jar differences are due to a latest version bump:
Code Block |
---|
< ./share/ozone/lib/jackson-annotations-2.10.3.jar
< ./share/ozone/lib/jackson-core-2.10.3.jar
< ./share/ozone/lib/jackson-databind-2.10.3.jar
< ./share/ozone/lib/jackson-dataformat-cbor-2.10.3.jar
< ./share/ozone/lib/jackson-dataformat-xml-2.10.3.jar
< ./share/ozone/lib/jackson-datatype-jsr310-2.10.3.jar
< ./share/ozone/lib/jackson-module-jaxb-annotations-2.10.3.jar
---
> ./share/ozone/lib/jackson-annotations-2.12.1.jar
> ./share/ozone/lib/jackson-core-2.12.1.jar
> ./share/ozone/lib/jackson-databind-2.12.1.jar
> ./share/ozone/lib/jackson-dataformat-cbor-2.12.1.jar
> ./share/ozone/lib/jackson-dataformat-xml-2.12.1.jar
> ./share/ozone/lib/jackson-datatype-jsr310-2.12.1.jar
> ./share/ozone/lib/jackson-module-jaxb-annotations-2.12.1.jar |
No new dependencies are added.
10. performance
Performance between master and SCM-HA branch (without turning on Ratis) is shared here
We use the default configuration for master and 2823.
The write throughput seems to be constrained by hardware, e.g. DC network, which we haven’t dug further.
According to the slight differences between 2823 and master, the performance of the SCM HA bypass Ratis is close to that of pure in-mem SCM
11. security considerations
Security is not ready on the branch yet, therefor this feature is not production-ready. SCM-HA is disabled for secure clusters to avoid any security issues. (See HDDS-4978.)None