Managing Cloudera Data Science Workbench Hosts

This topic describes how to perform some common tasks related to managing Cloudera Data Science Workbench hosts.

Migrating a Deployment to a New Set of Hosts

The following topics describe how to migrate a Cloudera Data Science Workbench deployment to a new set of gateway hosts.

Adding a Worker Node

Using Cloudera Manager

Perform the following steps to add a new worker node to Cloudera Data Science Workbench.
  1. Log in to the Cloudera Manager Admin Console.
  2. Add a new host to your cluster. Make sure this is a gateway host and you are not running any services on this host.
  3. Assign the HDFS, YARN, and Spark 2 gateway roles to the new host. For instructions, refer the Cloudera Manager documentation at Adding a Role Instance.
  4. Go to the Cloudera Data Science Workbench service.
  5. Click the Instances tab.
  6. Click Add Role Instances.
  7. Assign the Worker and Docker Daemon roles to the new host. Click Continue.
  8. Review your changes and click Continue. The wizard finishes by performing any actions necessary to add the new role instances. Do not start the new roles at this point. You must run the Prepare Node command as described in the next steps before the roles are started.
  9. The new host must have the following packages installed on it. 
    nfs-utils
libseccomp
lvm2
bridge-utils
libtool-ltdl
iptables   
rsync 
policycoreutils-python 
selinux-policy-base 
selinux-policy-targeted 
ntp 
ebtables 
bind-utils 
nmap-ncat  
openssl 
e2fsprogs 
redhat-lsb-core 
socat
    You must either manually install these packages now, or, allow Cloudera Manager to install them in the next step.

    If you choose the latter, make sure that Cloudera Manager has the permission needed to install the required packages. To do so, go to the Cloudera Data Science Workbench service and click Configuration. Search for the Install Required Packages property and make sure it is enabled.

  10. Click Instances and select the new host. From the list of available actions, select the Prepare Node command to install the required packages on the new node.
  11. On the Instances page, select the new role instances and click Actions for Selected > Start.

Using Packages

On an RPM deployment, the procedure to add a worker node to an existing deployment is the same as that required when you first install Cloudera Data Science Workbench on a worker. For instructions, see Installing Cloudera Data Science Workbench on a Worker Node.

Removing a Worker Node

Using Cloudera Manager

Perform the following steps to remove a worker node from Cloudera Data Science Workbench.
  1. Log into the Cloudera Manager Admin Console.
  2. Click the Instances tab.
  3. Select the Docker Daemon and Worker roles on the node to be removed from Cloudera Data Science Workbench.
  4. Select Actions for Selected > Stop and click Stop to confirm the action. Click Close when the process is complete.
  5. On the Instances page, re-select the Docker Daemon and Worker roles that were stopped in the previous step.
  6. Select Actions for Selected > Delete and then click Delete to confirm the action.

Using Packages

To remove a worker node:
  1. On the master node, run the following command to delete the worker node: 
    kubectl delete node <worker_node_domain_name>
  2. Reset the worker node. 
    cdsw reset

Changing the Domain Name

Cloudera Data Science Workbench allows you to change the domain of the web console.

Using Cloudera Manager

  1. Log into the Cloudera Manager Admin Console.
  2. Go to the Cloudera Data Science Workbench service.
  3. Click the Configuration tab.
  4. Search for the Cloudera Data Science Workbench Domain property and modify the value to reflect the new domain.
  5. Click Save Changes.
  6. Restart the Cloudera Data Science Workbench service to have the changes go into effect.

Using Packages

  1. Open /etc/cdsw/config/cdsw.conf and set the DOMAIN variable to the new domain name. 
    DOMAIN="cdsw.<your_new_domain>.com"
  2. Run the following commands to have the new domain name go into effect. 
    cdsw reset
cdsw init