My Oracle Support Banner

BDA Node Migration Fails at Step 7 Due to Balancer Running with "Swcleanup::Stopcloudera2/Exec[stop_cloudera_services]" (Doc ID 1957097.1)

Last updated on DECEMBER 09, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.0 and later
Linux x86-64

Symptoms

NOTE: In the images, examples and document that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

 

Step 7 of BDA node migration (or other server resilency command) fails with:

************************************
Error [6499]: (//bdanode01.example.com//Stage[main]/Swcleanup::Stopcloudera2/Exec[stop_cloudera_services]/returns) change fro\
m notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/stopscm.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/stopscm_14182497\
46.out returned 1 instead of one of [0]
************************************

1. Drilling down into the output file /opt/oracle/BDAMammoth/bdaconfig/tmp/stopscm_1418249746.out reports "Command 'Stop' failed for service 'hdfs'".

Succeeded.
Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_commands.out
API
Version used is v7
Succeeded. Output in :
/opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_<CLUSTER_NAME>-cluster_commands_stop.out
Command ID is
6853
Command 6853 finished after 5 seconds
Operation failed
Result Message is:
"Command 'Stop' failed for service 'hdfs'",

2. Further checking into commands_6853.out reports that the hdfs service can not be stopped due to: "There is already a pending command on this service."

{
 "id" : 6853,
 "name" : "Stop",
 "startTime" : "2014-12-10T22:19:47.115Z",

"endTime" : "2014-12-10T22:19:47.186Z",
 "active" : false,
 "success" : false,

"resultMessage" : "Command 'Stop' failed for service 'hdfs'",
 "clusterRef" :
{
   "clusterName" : "<CLUSTER_NAME>-cluster"
 },
 "children" : {
   "items" : [ {
     "id" : 6854,

"name" : "Stop",
     "startTime" : "2014-12-10T22:19:47.139Z",

"endTime" : "2014-12-10T22:19:47.139Z",
     "active" : false,

"success" : false,
     "resultMessage" : "There is already a pending command on this service.",

"serviceRef" : {
       "clusterName" : "<CLUSTER_NAME>-cluster",
       "serviceName" : "hdfs"
     }
   } ]
 }
}

 3. In Cloudera Manager (CM) > Commands,  the Balancer is observed to be running i.e. the command is "In Progress".

4. In CM navigating to Home > hdfs > instances > shows the Balancer is "Busy" which means it is running.

 

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!


In this Document
Symptoms
Cause
Solution


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