Ozone
You can review the list of reported issues and their fixes for Ozone in 7.3.1.200.
- CDPD-74556: EC Checksum throws IllegalArgumentException because the buffer limit is negative
- When ozone.client.bytes.per.checksum is set to a
lower value (for example, 16kb), the parity checksum calculation during validation phase is
wrong leading to IllegalArgumentException on client. This is now fixed.
Apache Jira: HDDS-11482
- CDPD-75981: Default native ACL limits to user and user's primary group
- Default native ACL created for an object such as volume, bucket, or
file limits to the object owner and owner's primary group.
Apache Jira: HDDS-11656
- CDPD-72782: Ozone write does not work when http proxy is set for the JVM
- GRPC uses HTTP internally for its connections and due to this, if HTTP
proxy is configured for any Ozone process using GRPC , it directs each call through the proxy
even for GRPC which is not desirable for performance. Hence this fix disables proxy for GRPC
connections that Ozone uses.
Apache Jira: HDDS-11257
- CDPD-65714: Allow FS client to specify EC as default filesystem replication
- This fix allows you to specify EC as the default replication type for
a file uploaded through the Hadoop FileSystem API to Ozone through a client side configuration
option.
Apache Jira: HDDS-10336