Behavioral Changes in Ozone

Functional adjustments and behavioral updates for Ozone are introduced in Cloudera Runtime 7.1.9 SP2.

Dynamic container sampling for SCM’s container replication manager

Previous behavior:Previously, the SCM’s container replication manager was hardcoded to sample only 100 containers per health state during each iteration.

New behavior:A new dynamically configurable property, hdds.scm.replication.container.sample.limit has been introduced to modify this value without requiring an SCM restart.

Ozone create, write, and delete operations now require Read permission

Previous behavior:

Creating, writing, or deleting an Ozone key did not require READ permission. If a user lacked access, the system returned a WRITE or DELETE permission denied error.

New behavior:

The Ozone Manager now checks permissions using the getFileStatus() API before creating, writing, or deleting. Users must have READ permission (or SELECT permission for Hive resources when Ranger RMS is enabled) for these actions to succeed. Unauthorized requests now return a READ permission denied error. This aligns with AWS S3 behaviour, preventing unauthorized users from checking whether a resource exists.