Start the ODP Stack Services

Start All Services Manually

Once the Ambari upgrade is done, start all the services manually and make sure it all started.

JDK 11 Env Changes

The following flags must be added after upgrading Infra-Solr, Hadoop, HBase, Hive, and Druid env files, before starting the services in a JDK11 environment.

Hadoop-env

The Java 11 flags have been addressed in the ${else} block, which needs to be updated after the upgrade is completed during the service start process.

File location: Log on to the Ambari UI → HDFSconfigsAdvanced -> Advanced hadoop-env -> hadoop-env template.

hadoop-env template
Copy

YARN-env

Update 1

Update the YARN Java 11 flags as shown below.

File location: Log into the Ambari UI and navigate to YARNConfigsAdvancedAdvanced yarn-hbase-envhbase-env template.

Bash
Copy

Replace it with the updated code block below.

Bash
Copy

Update 2

Update the YARN Java 11 flags as shown below.

File Location: Log into the Ambari UI and navigate to YARNConfigsAdvancedAdvanced yarn-hbase-envhbase-env template.

Bash
Copy

Replace it with the updated code block below.

Bash
Copy

Hbase-env

Update the HBase Java 11 flags as shown below.

File location: Log on to the Ambari UI → HBaseconfigsAdvanced hbase-env -> hbase-env template.

hbase-env template
Copy

Hive-env

Update 1

Update the Hive Java 11 flags in two places as shown below.

  • metastore
  • hiveserver2
  1. File location: Log into the Ambari UI → HiveConfigsAdvanced hive-envhive-env template.
hive-env template
Copy
  1. File location - Log into the Ambari UI → HiveConfigsAdvancedGeneral.
Configuration
Copy

Update 2

After completing the Ambari upgrade, during the express upgrade, you might see the below error while starting Hive metastore, due to a initSchema upgrade issue.

Bash
Copy

These issues occur because, after migrating to Hive 4.0.0, it is also necessary to upgrade the Hive Metastore database schema using the following commands.

Bash
Copy

The expected outcome is as follows.

Bash
Copy

Infra-solr-env

Update the Infra-Solr Java11 flags as shown below.

File location: Log into the Ambari UI → Infra SolrconfigsAdvanced Infr-Solr-env -> Infra Solr-env template.

druid-env template
Copy

Druid-env

Update the Druid Java-11 flags as shown below.

File location: Log on to the Ambari UI → DruidconfigsAdvanced druid-env.

Config Keys
Copy
Bash
Copy
Bash
Copy
Bash
Copy
Bash
Copy
Bash
Copy

Tez-env

Update the Tez Java11 flags as shown below.

File location: Log into the Ambari UI → TezConfigsAdvanced tez-env -> Tez-env template.

tez-env template
Copy

Update the custom Tez-site configurations as shown below.

Bash
Copy

Ranger KMS-env

For adding the Ranger-kms logback configuration, Navigate to Ranger-kms → Configs → Advanced -> Advanced kms-logback.

Bash
Copy

Following are the reference templates for making Java 11 runtime flags:

  1. Druid-env-template
  2. Hadoop-env-template
  3. Hbase-env-template
  4. Hive-env-template
  5. Infra-solr-env-template
  6. Tez-env-template
  7. Yarn-env-template
  8. Ranger-admin-logback.xml
  9. Ranger-kms-logback.xml
  10. Ranger-tagsync-logback.xml
  11. Ranger-usersync-logback.xml

Known Issues

During the ODP upgrade, where Ambari-2.7.9.x has already been upgraded, the following services might experience downtime. This downtime interrupts the ODP stack upgrade when using the express method.

Affected Services:

  • Ranger
  • Ranger KMS
  • HDFS
  • Kafka
  • Hive

Ranger

Issue 1: Ranger Admin service start

Error log
Copy

Solution:

  1. Log into the backend database for the Ambari-server.

    • In this case, MySQL is used as the Ambari server’s backend database.
  2. Execute the following SQL query to identify the required configurations.

MySQL
Copy
  1. The Expected Response is as follows.
MySQL
Copy
  1. Update the required configurations.
  • Ranger-admin service: Update admin-log4j to admin-logback
MySQL
Copy
  • Ranger tagsync service: Update tagsync-log4j to tagsync-logback
MySQL
Copy
  • Ranger usersync service: Update usersync-log4j to usersync-logback
MySQL
Copy
  1. Restart the Ambari-server.
Bash
Copy

Issue 2: Ranger Admin service start

Error log
Copy

Solution: Update the Ranger Configuration

  1. Log into the Ambari UI → RangerConfigsAdvancedAdvanced admin-logback.

Replace the admin-logback-xml template with the one below.

admin-logback-xml
Copy
  1. On the Ambari UI, navigate to RANGERCONFIGS -> ADVANCED -> Advanced tagsync-logback, update with the following content, and save.
Bash
Copy
  1. On the Ambari UI, navigate to RANGERCONFIGS -> ADVANCED -> Advanced usersync-logback, update with the following content, and save.
Bash
Copy

You can now proceed with the Ranger service restart from the Ambari UI. It must start smoothly.

Ranger KMS

During the cluster upgrade (after Ambari is upgraded to 2.7.9.x but before the ODP stack is upgraded), the Ranger-KMS service might not start due to the following error:

Error log
Copy

Kms-log4j is replaced with kms-logback starting from version 3.2.3.x.

Solution:

Log into the backend database for the Ambari server.

In this case, MySQL is the backend database for the Ambari server.

MySQL
Copy
  • Response:
Response
Copy

Ranger-Admin Service Required Change

Update kms-log4j to kms-logback:

MySQL
Copy

From the Ambari-Server host, perform the following steps:

  1. Edit the File:

Path: /var/lib/ambari-server/resources/stacks/ODP/3.0/services/RANGER_KMS/package/scripts/kms.py

Locate the following lines:

Python
Copy

Comment them out as shown below:

Bash
Copy
  1. Restart the Ambari-Server.
Bash
Copy

You can now proceed with restarting the Ranger-KMS service from the Ambari UI. It must start smoothly.

Update the Ranger KMS Configuration

  1. Log into the Ambari UI and navigate to RANGERCONFIGS -> ADVANCED -> Advanced admin-logback, update the following content, and save.
Bash
Copy
  1. Restart the Ranger KMS service from the Ambari UI.

HDFS

Name node or any service fails - rangerlookup not found

Error log
Copy

Solution:

Add rangerlookup in the Ranger users list.

Data Node Start Issue

In upgraded clusters, the DataNodes fail to start and hang forever without much logging:

Error log
Copy

There will be no more logging after that, will be timed out later.

Solution:

Log on to the Ambari UI → HDFSconfigsAdvancedcustom hdfs-rbf-site

Bash
Copy

Complete the configurations template for custom hdfs-rbf-site.

DFSRouter component configs list

If the router component is to be used in the ODP cluster, add the below configurations.

Log on to the Ambari UI → HDFSconfigsAdvancedcustom hdfs-rbf-site.

custom hdfs-rbf-site
Copy

Node manager start failed

Bash
Copy

Solution:

  • Remove the following from yarn configurations:

    • spark_shuffle from yarn.nodemanager.aux-services
  • Remove the following from Custom yarn-site:

Custom yarn-site
Copy

Kafka

After completing the Ambari upgrade, during the express upgrade, Kafka needs to be up and running in a healthy mode. However, Kafka might be in a stopped state due to the following errors:

Error
Copy

These issues occur because Kafka Connect and MirrorMaker were added in this release.

Solution

To start Kafka, add the following configurations in Ambari:

  1. Custom kafka-mirrormaker2-common

    • replication.factor =1
  2. Custom kafka-mirrormaker2-destination

    • replication.enabled=true
    • destination.cluster.name=dest
    • topics.whitelist=.*
  3. Custom kafka-mirrormaker2-source

    • replication.enabled=true
    • source.cluster.name=source
    • topics.whitelist=.*
  4. Custom kafka-connect-distributed

    • bootstrap.servers=localhost:6667

Proceed with restarting the Kafka service. It must start smoothly.

###

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
  Last updated