On BDA V4.7 with Big Data SQL 3.1 Adding a Service in Cloudera Manager Fails (Doc ID 2272620.1)

Last updated on JUNE 01, 2017

Applies to:

Big Data Appliance Integrated Software - Version 4.7.0 to 4.7.0 [Release 4.7]
Oracle Big Data SQL - Version 3.1.0 to 3.1.0 [Release 3.1]
Linux x86-64

Symptoms

On a BDA V4.7 cluster with Big Data SQL 3.1 installed, adding a service in Cloudera Manager (CM) fails.

Using an example of adding the Sqoop 1 Client service, navigating in CM:

Home > Add Service > Sqoop 1 Client > Page 1 select Gateway > Page 3 Add Sqoop 1 Client Service to <cluster> First Run Command  fails with:

a) A failure on page 3, Add Sqoop 1 Client Service to <cluster>:

First Run Command
Status Failed

Failed to perform First Run of services.

All Failed Only Running Only
Details
Completed 1 of 2 step(s).

Run 5 steps in parallel

Completed only 4/5 steps. First failure:
Timed out after 120000 ms.
Waiting for Cloudera Manager Agents to detect release:
BIGDATASQL 3.1.0. Host(s) missing this release:
bdanode[01-05].example.com

b) A failure like:

Waiting for Cloudera Manager Agents to detect release:
BIGDATASQL 3.1.0. Host(s) missing this release: bdanode[01-05].example.com

Timed out after 120000 ms. Waiting for Cloudera Manager Agents
to detect release: BIGDATASQL 3.1.0.
Host(s) missing this release: bdanode[01-05].example.com

 

Cause

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 hundreds of Community platforms