Hui, Wei-Chiu, Peter, Chung En, Sammi
- Ozone 2.2.0 release discussion. 2.2.0 will target to include following
features
- https://issues.apache.org/jira/browse/HDDS-13323 STS
- https://issues.apache.org/jira/browse/HDDS-8342 S3 Lifecycle
- https://issues.apache.org/jira/browse/HDDS-5713 disk balancer
- https://issues.apache.org/jira/browse/HDDS-14424 Follower Read
- https://issues.apache.org/jira/browse/HDDS-10338 new readBlock API
- Apache CoC Apache call for proposal
https://sessionize.com/community-over-code-asia-2026/ deadline April 21th
- Performance testing, RATIS improvements(
https://issues.apache.org/jira/browse/RATIS-2129) and new readBlock API
- Support direct data copy to GPU through RDMA investigation
- MultipartUpload improvement,
https://issues.apache.org/jira/browse/HDDS-10611
- Problems found recently
- DN segment fault crash due to rocksdb close,
https://issues.apache.org/jira/browse/HDDS-14800
- Bottleneck of EC data decommission. Current implementation is copying
the decommissioned replica directly the datanode to target node
- After upgrade to JDK 21, ZGC causes process hang due to huge-page
allocation
- Datanode memory leaks,
https://issues.apache.org/jira/browse/RATIS-2421(under review),
https://issues.apache.org/jira/browse/RATIS-2427(merged)
- Provide single docker node Ozone cluster, so new user can try out Ozone
easily, https://issues.apache.org/jira/browse/HDDS-14893
- S3 signed multi chunks payload signature is not verified,
https://issues.apache.org/jira/browse/HDDS-12542
