Known Issues in Ozone
Learn about the known issues in Ozone, the impact or changes to the functionality, and the workaround.
- CDPD-15268:
- Uploading a key using the S3 Multi-part upload API into an Ozone encryption zone (TDE-enabled bucket) is not currently supported. The key upload will fail with an exception.
- CDPD-15602: Creating or deleting keys with a trailing forward slash (/) in the name is not supported via the Ozone shell or the S3 REST API. Such keys are internally treated as directories by the Ozone service for compatibility with the Hadoop filesystem interface. This will be supported in a later release of CDP.
- You can create or delete keys via the Hadoop Filesystem
interface, either programmatically or via the filesystem Hadoop shell. For
example,
ozone fs -rmdir <dir>. - CDPD-21837:
- Adding new Ozone Manager (OM) role instances to an existing cluster will cause the cluster to behave erratically. It can possibly cause split-brain between the Ozone Managers or crash them.
- OPSAPS-59647:
- Ozone has an optional role where it can deploy a pre-configured Prometheus instance. This prometheus instance's default port '9090' conflicts with HBase Thrift Server's port. Hence, one of the components will fail to start if they are on the same host.
- CDPD-24321:
- On a secure cluster with Kerberos enabled, the Recon dashboard shows a value of zero for volumes, buckets, and keys.
