Learn about the known issues in Ozone, the impact or changes to the functionality,
and the workaround.
Known Issues identified in Cloudera Runtime 7.3.1.706 SP3 CHF
2
There are no new known issues identified in this release.
Known Issues identified in Cloudera Runtime 7.3.1.600 SP3 CHF
1
CDPD-91562:
test_validate_certs_configs configuration is failing
with the maximum lifetime validation
7.3.1.600
In daylight saving time zones, the autogenerated Ozone
certificate duration might differ from the expected duration. This
discrepancy is minor, because the default certificate duration is 365 days
or five years, depending on the Ozone component.
Known Issues identified in Cloudera Runtime 7.3.1.500
SP3
There are no new known issues identified in this release.
Known Issues identified in Cloudera Runtime 7.3.1.400
SP2
CDPD-87097: Installation fails with a
NullPointerException (NPE) in the Ozone-Recon log
7.3.1.600
7.3.1.400, 7.3.1.500
This is a known intermittent issue in 7.3.1.400. NPE
thrown does not tell the actual cause and this intermittent issue is not
reproducible as this comes sometimes during first run of installalation of
the cluster. This looks to be more of an CDEP environment issue.
CDPD-75954: The ozone debug ldb
command and ozone auditparser fails with
java.lang.UnsatisfiedLinkError
The Ozone client cannot be used to read or
write encrypted data to multiple Ozone clusters using different KMS's for
encrypted key management. This is because Ozone client uses KMS provider URI
specified in the client side configurations instead of using the provider
presented by multiple Ozone Managers.
None
CDPD-54885: Ozone Prometheus does not work with
TLS
7.3.1 and it's higher versions
The Prometheus service shipped by Ozone does not
support TLS mode. So, Prometheus is not able to gather metrics from Ozone
endpoints when TLS is enabled.
Go to Ozone > Configuration > Ozone Prometheus Endpoint Token and update the Ozone Prometheus Endpoint
Token with any random string. This makes a token available
in the process directory of the Ozone endpoint in plaintext, which
Prometheus can use to get around the TLS limitation.
CDPD-56684: Keys get deleted when you do not have
permission on volume
7.3.1 and it's higher versions
When a volume is deleted, it recursively deletes the
buckets and keys inside it and only then deletes the volume. The volume
delete ACL check is done only in the end, due to which you may end up
deleting all the data inside the volume without having delete permission on
the volume.
CDPD-50610: Large file uploads are slow with OPEN and
stream data approach
7.3.1 and it's higher versions
Hue file browser uses the append operation for large
files. This API is not supported by Ozone in 7.1.9 and therefore large file
uploads can be slow or timeout from the browser.
Use native Ozone client to upload large files
instead of the Hue file browser.
OPSAPS-66469: Ozone-site.xml is missing if the host
does not contain HDFS roles
7.3.1 and it's higher versions
The client side ozone-site.xml
(/etc/hadoop/conf/ozone-site.xml) is not generated
by Cloudera Manager if the host does not have any HDFS
role. Because of this, issuing Ozone commands from that host fails because
it cannot find the service name to host name mapping. The error message is
similar to this: # ozone sh volume list o3://ozoneabc 23/03/06
18:46:15 WARN ha.OMProxyInfo: OzoneManager address ozoneabc:9862 for
serviceID null remains unresolved for node ID null Check your
ozone-site.xml file to ensure ozone manager addresses are configured
properly.
Add the HDFS gateway role on that host.
CDPD-74016: Running Ozone sh token print on token generated
using ozone dtutil command results in Null Pointer
Exception.
Print the token generated by dtutil using
dtutil.
CDPD-74013: Ozone dtutil get token fails when using o3 or
ofs schemas.
Use ozone sh token get to get a token for ozone
file system.
CDPD-63144: Key rename inside the FSO bucket fails and
discplays the Failed to get parent dir error. This happens
when running impala workloads with ozone.
None.
CDPD-74331: Key put fails and displays the Failed to
write chunk error when there is a volume failure during
configuration.
None.
CDPD-74475: YCSB test with Hbase on Ozone degrades
performance.
7.3.1 and it's higher versions
None.
CDPD-74884: Exclusive size of snapshot is always 0 when you
run the info command on the Ozone snapshots. It is a
statistics issue and does not impact the functionality of Ozone
snapshot.
7.3.1 and it's higher versions
exclusiveSize and exclusiveReplicationSize
stats presented by `snapshot info` are 0 even though the snapshot contains
exclusive keys or files that are not present in other snapshots.
None.
CDPD-75042: AWS CLI rm or
delete command fails to delete all files and
directories on the Ozone FSO bucket. It only deletes the leaf node.
7.3.1 and it's higher versions
None.
CDPD-75204: Namenode restart fails after
dfs.namenode.fs-limits.max-component-length is set
to a lower value and there is existing data present which exceeds the length
limit.
7.3.1 and it's higher versions
Increase the value for the
dfs.namenode.fs-limits.max-component-length
parameter and restart the namenode.
CDPD-75635: Ozone write fails intermittently as SCM remains
in safemode.
7.3.1 and it's higher versions
You must wait for SCM to come out of samemode or
exit from safemode through CLI options.
CDPD-74257: For the 7.3.1 release, the Heatmap feature
is disabled and removed from the Recon UI and the Solr health check is
removed from the Recon Overview page.
7.3.1.0
If the APIs are called, heatmap APIs will block
threads if the javax.security.auth.useSubjectCredsOnly
property is set to true.
To check if javax.security.auth.useSubjectCredsOnly
is set to true, you can run the sudo -u
hdfs /usr/java/jdk1.8.0_232-cloudera/bin/jcmd <PID>
VM.system_properties | grep -i subject command where PID
must be replaced with Recon process id.
To identify the PID, run ps -ef and
grep for Recon to find the Java process running
Recon.
