Cloudera Docs

Known Issues

You must be aware of the known issues and limitations, the areas of impact, and workaround in Cloudera Manager 7.13.3 and its cumulative hotfixes.

Known issues identified in Cloudera Manager 7.13.3.0

OPSAPS-81194: Cloudera Manager Server experiences memory leaks and potential Out Of Memory (OOM) errors due to unclosed NettyTransceiver connections
7.13.3.0

In Cloudera Manager 7.13.3.0, Cloudera Manager Server leaks Avro RPC publisher connections (NettyTransceiver) to the Event Server approximately once every minute. Over time, these unclosed connections accumulate threads, connections, and heap memory, eventually causing Cloudera Manager Server to run out of memory (OOM) and crash.

This issue affects installations running Cloudera Manager 7.13.3.0.
Periodically restart the Cloudera Manager Server before JVM memory usage reaches its limit. Restarting the server releases all leaked threads, active network connections, and consumed memory.
  1. Check the current thread and Event Server connection counts on the Cloudera Manager Server host:
    ps -o nlwp=,rss= -p $(pgrep -f com.cloudera.server.cmf.Main)
ss -tn | grep -c ':7184'

    While this issue persists, both values increase by approximately 1,440 per day.

  2. Restart the Cloudera Manager Server:
    sudo systemctl restart cloudera-scm-server
  3. Schedule a recurring restart interval based on your observed resource growth rate. For example, a server using the default 8 GB Java heap typically requires a restart every 5 to 7 days to maintain an adequate memory buffer.
CDPD-99324: Livy gateway role is available only on the first Livy for Spark 3 service
7.13.3.0

When a cluster has more than one Livy for Spark 3 service, for example to place several Livy for Spark 3 service instances behind a load balancer, Cloudera Manager supports the Livy gateway role only on the first Livy for Spark 3 service. You cannot add the gateway role to the second or any later Livy for Spark 3 service.

Add the Livy gateway role only to the first Livy for Spark 3 service. Point clients to the client-facing URL of the load balancer, or to Knox, instead of to an individual Livy for Spark 3 service. For more information, see Livy load balancing with HAProxyLivy load balancing with HAProxy.