Cloudera Docs

cdp-doctor scm describe-command --name <CommandName>

Scope

The cdp-doctor scm describe-command --name command provides detailed information about a specific command executed by the Cloudera Manager (SCM). It displays the command name, unique ID, and exit status, helping administrators verify whether a particular SCM operation completed successfully or failed.

This command is typically used after reviewing the output of cdp-doctor scm list-commands to examine the results of specific commands

Use Case

  • Verifying the success or failure of a specific Cloudera Manager command.
  • Troubleshooting failed SCM operations identified with the cdp-doctor scm list-commands command.

Sample Output

The cdp-doctor scm describe-command --name command retrieves detailed metadata about SCM operations, such as:

Field Description
Command id Unique numeric identifier for the executed command.
Command Name The specific operation name (e.g., hbase-export, hdfs-NAMENODE-format).
Exit Code Execution result:
  • 0: Success
  • 1: Failure or error occurred
Successful Command

Running the cdp-doctor scm describe-command --name hdfs-NAMENODE-format command displays the following output:

==============
Command Id: 1546336737
Command Name: hdfs-NAMENODE-format
Exit Code: 0
==============

The command executed successfully (Exit Code 0). hdfs-NAMENODE-format indicates that the HDFS NameNode was formatted correctly — a crucial initialization step during cluster setup.

Failed Command

Running the cdp-doctor scm describe-command --name hbase-export command displays the following output:

==============
Command Id: 1546363045
Command Name: hbase-export
Exit Code: 1
==============
==============
Command Id: 1546363038
Command Name: hbase-export
Exit Code: 1
==============

Both hbase-export commands failed (Exit Code 1). These are typically part of the HBase snapshot or export process, and failure may indicate an issue with:

  • HBase service availability
  • Permission errors
  • Misconfigured export directories

You can further investigate the issue with the HBase service logs.