Known Issues in Cloudera Manager 7.4.2
This topic describes known issues and workarounds for Cloudera Manager.
- Cloudera bug: OPSAPS-59764: Memory leak in the Cloudera Manager agent while downloading the parcels.
-
When using the M2Crpyto library in the Cloudera Manager agent to download parcels causes a memory leak.
The Cloudera Manager server requires parcels to install a cluster. If any of the URLs of parcels are modified, then the server provides information to all the Cloudera Manager agent processes that are installed on each cluster host.
The Cloudera Manager agent then starts checking for updates regularly by downloading the manifest file that is available under each of the URLs. However, if the URL is invalid or not reachable to download the parcel, then the Cloudera Manager agent shows a 404 error message and the memory of the Cloudera Manager agent process increases due to a memory leak in the file downloader code of the agent.
- Cloudera bug: OPSAPS-63881: When CDP Private Cloud
Base is running on RHEL/CentOS/Oracle Linux 8.4, services fail to start because service
directories under the
/var/lib
directory are created with 700 permission instead of 755. - Run the following command on all managed hosts to change the
permissions to 755. Run the command for each directory under
/var/lib
:chmod -R 755 [***path_to_service_dir***]
- OPSAPS-65189: Accessing Cloudera Manager through Knox displays the following error:
Bad Message 431 reason: Request Header Fields Too Large
Workaround: Modify the Cloudera Manager Server configuration /etc/default/cloudera-scm-server file to increase the header size from 8 KB, which is the default value, to 65 KB in the Java options as shown below:export CMF_JAVA_OPTS="...existing options... -Dcom.cloudera.server.cmf.WebServerImpl.HTTP_HEADER_SIZE_BYTES=65536 -Dcom.cloudera.server.cmf.WebServerImpl.HTTPS_HEADER_SIZE_BYTES=65536"