Cloudera Docs

Known issues in Ozone

Learn about the known issues in Ozone, the impact or changes to the functionality, and the workaround.

CDPD-87429: Unexpected log lines in Ozone snapshot diff output
`ozone.client.server-defaults.validity.period.ms` configuration introduced to get server default configurations causes Replication Manager to fail when replicating data between Ozone buckets with the following error when the config value does not specify a timeunit.
```
java.lang.IllegalStateException: Invalid first line in diff: "25/07/02 05:58:44 INFO Configuration.deprecation: No unit for ozone.client.server-defaults.validity.period.ms(3600000) assuming MILLISECONDS"
	at com.cloudera.enterprise.distcp.OzoneCopyListingUtils.parseOzoneDiff(OzoneCopyListingUtils.java:397)
```
Overwrite the `ozone.client.server-defaults.validity.period.ms` to configure the value to have time unit (ns, ms, s, m, h). For example, 3600000ms.
CDPD-71648: Snapshot creation failing with "PERMISSION_DENIED" error on a bucket created during pre-upgrade in 7.1.7 SP3
On upgrade of cluster from 7.1.7 SP3 to 7.1.9 SP1, we are not able to create snapshots on a pre-upgrade volume or bucket with "PERMISSION_DENIED" error, since in 7.1.7SP3, we were using full KRB owner name with domain but currently, we only use and search for user shortname.
Update the owner of the bucket with the user shortname and then create snapshot by running the commands: 
ozone sh bucket update --user={[***USER_SHORT_NAME***]} {volume}/{bucket}
ozone sh snapshot create {volume}/{bucket} {[***SNAPSHOT_NAME***]}
OPSAPS-74668: ozone.snapshot.deep.cleaning.enabled and ozone.snapshot.ordered.deletion.enabled configurations are missing with CDP 7.1.9 SP1 CHF and Cloudera Manager 7.13.1
Two Ozone Manager configurations are missing while using CDP 7.1.9 SP1 CHF after upgrading Cloudera Manager version from 7.11.3 to 7.13.1.400.
If you are using CDP 7.1.9 SP1 CHF, before upgrading Cloudera Manager version from 7.11.3 to 7.13.1.400, add the following configs to Ozone Manager Advanced Configuration Snippet (Safety Valve) for ozone-conf/ozone-site.xml so that Ozone Manager does not miss important config after the Cloudera Manager upgrade:
<property>
<name>ozone.snapshot.deep.cleaning.enabled</name>
<value>false</value>
</property>

<property>
<name>ozone.snapshot.ordered.deletion.enabled</name>
<value>true</value>
</property>