You must complete the post transition steps to start the services in Cloudera Private Cloud Base .
The AM2CM tool transitions the service configurations. However, you must configure and
perform additional steps to start the services in Cloudera Private Cloud Base .
note
Review configuration warnings for all the services.
Review JVM parameters and configurations for all services as some of the JVM parameters
and configurations are not transitioned. Most of the heap configurations are
transitioned.
Review the Log4j configurations. Log4j configurations
such as logs dir, size, and backup index are transitioned to Cloudera Manager.
Spark Atlas Connector (SAC) is disabled by default. If you enable SAC on HDP, the Spark
entities are created using the Spark model (spark_db, spark_table). In CDP Private Cloud
Base, SAC uses HMS and the entities are created using the Hive model (hive_db, hive_table,
and hive_column). Hence Spark model entities in HDP are not in sync with the Hive model
entities in CDP Private Cloud Base. In CDP Private Cloud Base, the lineage stitching and
metadata update is not available on the Spark entities created in HDP.
In the HDP 3.1.5.x cluster, Hive hook and HBase hook are enabled by default. SAC (Spark
Atlas Connector or Spark Hook) is disabled by default. Note that, in HDP, SAC is in a
Technical Preview state. In CDP Private Cloud Base, Hive Hook and HBase hook are enabled
by default, In the AM2CM upgrade flow, if the Hive Hook and HBase hook are enabled in the
HDP-3.1.5.x cluster, post-upgrade, it is enabled in CDP Private Cloud Base. HMS Hook
functionality did not exist in HDP 3.1.5.x, hence it must be manually enabled in CDP
Private Cloud Base. Similarly SAC in CDP Private Cloud Base must also be manually enabled.
There are no manual steps required to enable SSO for the services on CDP. SSO is
available by default on CDP.
