Cloudera Data Science Workbench Command Line Reference
This topic describes the commands available with the Cloudera Data Science Workbench command line utility, cdsw. Running cdsw without any arguments will print a brief description of each command.
Start, Stop, Restart for CSD Deployments: The commands available for a CSD-based deployment are only a subset of those available for an RPM deployment. For example, the CLI for CSD deployments does not have commands such as cdsw start, stop, and restart available. Instead, these actions must be executed through the Cloudera Data Science Workbench service in Cloudera Manager. For instructions, see Starting, Stopping, and Restarting the Service.
Command | CSD | Description and Usage |
---|---|---|
cdsw init |
Initializes and bootstraps the master node. Use this command to start Cloudera Data Science Workbench. Also see, Additional Usage Notes |
|
cdsw start |
Run on the master node to start application components. |
|
cdsw stop |
Run on the master node to stop application components. |
|
cdsw restart |
Run on the master node to restart application components. To restart a worker node, use cdsw reset, followed by cdsw join. These commands have been explained further in this topic. |
|
cdsw reset |
De-registers and resets a node. On a worker node, this command will remove the worker from the cluster. On the master node, this command will bring down the application and effectively tear down the Cloudera Data Workbench deployment. |
|
cdsw join |
Initializes a worker node. After a worker node has been added, run this command on the worker node to add it to the Cloudera Data Science Workbench cluster. This registers the worker nodes with the master, and increases the available pool of resources for workloads. |
|
cdsw status |
Displays the current status of the application. Starting with version 1.4, you can use cdsw status -v or cdsw status --verbose for more detailed output. |
|
cdsw validate |
Performs diagnostic checks for common errors that might be preventing the application from running as expected. This command should typically be run as the first step to troubleshooting any problems with the application, as indicated by cdsw status. |
|
cdsw logs |
Creates a tarball with diagnostic information for your Cloudera Data Science Workbench installation. If you file a case with Cloudera Support, run this command on each node and attach the resulting bundle to the case. For more details on the information collected in these bundles, see Data Collection in Cloudera Data Science Workbench. |
|
cdsw version |
Displays the version number and type of Cloudera Data Science Workbench deployment (RPM or CSD). |
|
cdsw help |
Displays the inline help options for the Cloudera Data Science Workbench CLI. |
Additional Usage Notes
- Master Node - Changes to the JAVA_HOME, MASTER_IP, DOCKER_BLOCK_DEVICES, and APPLICATION_BLOCK_DEVICE parameters in cdsw.conf require a re-initialization of the master
node.
cdsw reset cdsw init
Changes to other cdsw.conf parameters such as domain name changes, or TLS and HTTP proxy changes, require a restart of the application components.cdsw restart
- Worker Node - Changes to cdsw.conf on a worker node, require a restart of the worker node as follows:
cdsw reset cdsw join