Hadoop-env

The Java 11 flags are handled in the ${else} block and must be updated after the upgrade is complete during the service start process.

File location: Log in to the Ambari UI → HDFS → Configs → Advanced → Advanced hadoop-env → hadoop-env template.

hadoop-env template
Copy

Issue 1: DataNode Start Issue During Upgrade

In upgraded clusters, DataNodes fail to start and hang indefinitely with minimal logging. The logs stop after entries similar to the following:

Bash
Copy

No further logging is generated, and the service eventually times out.

Solution

  1. Log in to the Ambari UI.
  2. Navigate to HDFS → Configs → Advanced → custom hdfs-rbf-site.
  3. Add or update the following property:
Bash
Copy
  1. Save the configuration and restart the affected DataNodes.

Issue 2: Data Node Start Issue During Upgrade

After upgrading from 3.2.3.x to 3.3.6.x, the DataNode may fail to start with errors such as:

Error
Copy

The bigtop-jsvc package from the old version may still be installed:

Bash
Copy

Since the 3.3.6.x version of bigtop-jsvc is not installed, the DataNode startup fails.

Workaround / Fix:

  1. Install the latest bigtop-jsvc package for 3.3.6.x:

On RHEL 8/9:

Bash
Copy

Ubuntu 20/22:

Bash
Copy
  1. Restart the DataNode service.
  2. Verify the installed version:
Bash
Copy

DFSRouter component configs list

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

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

custom hdfs-rbf-site
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
  Last updated