...
Git Branch: https://github.com/apache/ozone/tree/HDDS-3816-ec
Branch merge checklist
1. builds/intermittent test failures
There are no intermittent failures specific to the HDDS-3861-ec 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
Described feature in Apache ozone page via
...
Jira | ||||||
---|---|---|---|---|---|---|
|
- hadoop-hdds/docs/content/feature/ErasureCoding.md has the feature details and related configurations.
3. design, attached the docs
Following design docs are linked from the documentation present in
...
jira Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key HDDS-6172
- Design Document
- hadoop-hdds/docs/content/feature/hadoop-hdds/docs/content/feature/ErasureCoding.md has the feature details and related configurations.
4. s3 compatibility
EC feature does not beak any existing S3 compatibility. Please note S3 support is not ready yet for EC though. But this should not be a blocker for merge.
5. docker-compose / acceptance tests
Acceptance tests added
...
Jira | ||||||
---|---|---|---|---|---|---|
|
6. support of containers / Kubernetes:
NA. Deployment model for OzoneManager remains as earlier.
7. coverage/code quality:
Sonar master branch
Sonar HDDS-3816-ec branch.
The branch has better coverage than master (68% vs 72%)
8. build time
There is no significant difference between local build time.
...
Recent HDDS-3816-ec branch build
- test time of acceptance unsecure is increased with ~3 minutes
- integration test is increased with ~4 mins
9. possible incompatible changes/used feature flag:
For using this feature, users create bucket with EC replication config, so that the keys created in that bucket will be written in EC mode.
Upgrade: Before finalization, we would like to reject EC related requests. Even though EC feature not introduced any new APIs, but parameters carry different values to indicate EC options. So, We needed some special handling to check the parameters level and validate the requests. Related upgrade JIRAs being worked on are:
and Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key HDDS-6213 Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key HDDS-5909
Compatibility Changes: Currently forward compatibility broken due to the introduction if server side defaults and removal of client side default configurations. This is also being work on Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key HDDS-6209
We are tracking down the above issues before the merge.
10. third party dependencies/licence changes:
No new dependencies are added.
11. performance
There should not be any performance impact for Non-EC flows. For EC files there is basic benchmark performed here
. Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key HDDS-6194
12. security considerations
Everything works as earlier and there is no security implications because of the feature.