Known issues and technical limitations for Livy are addressed in Cloudera Runtime 7.3.3.
Known issues identified in Cloudera Runtime 7.3.3
- CDPD-99324: Livy gateway role is available only on the first
Livy for Spark 3 service
- 7.3.3
- When a cluster has more than one Livy for Spark 3
service, for example to run several Livy for Spark 3 service instances behind HAProxy,
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
HAProxy.
- CDPD-99323: Knox topologies include the Livy Server roles of
every Livy for Spark 3 service
- 7.3.3
- When a cluster has more than one Livy for Spark 3
service, Knox service discovery adds every Livy Server role of every Livy for Spark 3
service to the
LIVY_FOR_SPARK3 service in the
cdp-proxy, cdp-proxy-api, and
cdp-proxy-token topologies. Knox then routes Livy requests to roles
that you did not intend to expose through Knox, and the Livy UI can be empty or show
sessions from the wrong service.
- In Cloudera Manager, use the Knox
Safety Valve to define the Livy Server URLs that each topology exposes. The explicit
URLs override the URLs that Knox discovers. For more information, see Configuring Knox topologies for
multiple Livy for Spark 3 services.
Known issues identified before Cloudera Runtime 7.3.3
Known issues identified before Cloudera Runtime 7.3.3 include only
unresolved issues from previous releases that continue to affect the Cloudera Runtime 7.3.3 release.
- CDPD-102241: Missing Livy for Spark 3 logo in Knox UI
- 7.3.3, 7.3.2.10000 SP1
- The Knox Gateway UI does not display the Livy for Spark 3
service logo.
- None.