My Oracle Support Banner

Extending a Node into a BDA 4.10/CDH 5.12.1 Cluster Fails on Step 8, Starting Hadoop Services, When Deploying the Client Configuration Due to Incorrect Alternatives (Doc ID 2414452.1)

Last updated on JULY 07, 2018

Applies to:

Big Data Appliance Integrated Software - Version 4.10.0 and later
x86_64

Symptoms

Extending a node into a BDA 4.10/CDH 5.12.1 cluster fails on Step 8 "Starting Hadoop Services" when deploying the client configuration. Navigating in Cloudera Manager to: All Recent Commands, shows that the reason "Deploy Client Configuration" is failing is due to the hive client configuration failing to deploy on one node of the cluster.

For example

1. Navigating in Cloudera Manager (CM) to: All Recent Commands, shows:

Deploy Client Configuration Command
Status Failed Context hive <timestamp>
Deploy Client Configuration failed
Completed 1 of 1 step(s)

Generate and deploy client configuration
Timed out after 180000 ms. Completed only 18/29 steps. First failure: No response from host bdanode0x.example.com

2. /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_cmd.out shows the failure to be for deploying the hive client configuration:

{
"id" : <###>,
"name" : "deployClientConfig",
"startTime" : "<timestamp>",
"endTime" : "<timestamp>",
"active" : false,
"success" : false,
"resultMessage" : "Deploy Client Configuration failed.",
"serviceRef" : {
"clusterName" : "cluster",
"serviceName" : "hive"
}

There are no related errors in /var/log/hive and all the nodes have the hive gateway role and look to be as expected. It is also the case that the node where "Deploy Client Configuration" fails for hive is heartbeating into the cluster.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.