Upgrading Cloudera Data Science Workbench 1.8.0 Using Cloudera Manager
Before you begin the upgrade process, make sure you read the Cloudera Data Science Workbench Release Notes relevant to the version you are upgrading to/from.
- (Upgrading from CDSW 1.7.1 with patch) Perform this step only if you are upgrading from CDSW 1.7.1 with an applied
- Delete the 2 patch files: /etc/cdsw/patches/default/deployment/ingress-controller.yaml and /etc/cdsw/patches/default/deployment/tcp-ingress-controller.yaml.
- Delete every empty folder from the /etc/cdsw/patches directory.
- Delete the /etc/cdsw/patches directory if it is empty.
- (Strongly Recommended) On the master host, backup all your application data that is stored in the /var/lib/cdsw directory.
To create the backup, run the following command on the master host:
tar cvzf cdsw.tar.gz /var/lib/cdsw/*
Deactivate the existing Cloudera Data Science Workbench parcel. Go to the Cloudera Manager Admin Console. In the top navigation bar, click.
Locate the current active CDSW parcel and click Deactivate. On the confirmation pop-up, select Deactivate Only and click OK.
- Download and save the latest Cloudera Data Science Workbench CSD to the Cloudera Manager Server host.
Download the Cloudera Data Science Workbench CSD. Make sure you download the CSD that corresponds to the version of CDH or Cloudera Runtime you are using.
CDP Data Center
- Log on to the Cloudera Manager Server host, and place the CSD file under /opt/cloudera/csd, which is the default location for CSD files.
- Delete any CSD files belonging to older versions of Cloudera Data Science Workbench from /opt/cloudera/csd.
This is required because older versions of the CSD will not work with the latest Cloudera Data Science Workbench parcel. Make sure your CSD and parcel are always the same version.
After you delete the file(s) belonging to the older version, you should still have two files for the current version; one for CDH5 (for example, CDSW1.8-CDH5..jar) and one for CDH6 (for example, CDSW1.8-CDH6..jar). You'll need both of these files to upgrade.
- Set the CSD file ownership to cloudera-scm:cloudera-scm with permission 644.
- Restart the Cloudera Manager Server:
service cloudera-scm-server restart
- Log into the Cloudera Manager Admin Console and restart the Cloudera Management Service.
- Select .
- Select .
- Distribute and activate the new parcel on your cluster.
- Log into the Cloudera Manager Admin Console.
- Click in the main navigation bar.
- If the latest CDSW parcel is already available in this list, you can skip this step.
Add the Cloudera Data Science Workbench parcel repository URL to Cloudera Manager.
- On the Parcels page, click Configuration.
- In the Remote Parcel Repository URLs list, click the addition symbol to create a new row.
- Enter the path to the repository.
Version Remote Parcel Repository URL Cloudera Data Science Workbench 1.8.0
- Click Save Changes.
- Go back to the Download. Once the download is complete, click Distribute to distribute the parcel to all the CDH hosts in your cluster. Then click Activate. For more detailed information on each of these tasks, see Managing Parcels. page. The latest parcel should now appear in the set of parcels available for download. Click
Run the Prepare Node command on all Cloudera Data Science Workbench hosts.
Before you run Prepare Node, you must make sure that the command is allowed to install all the required packages on your cluster. This is controlled by the Install Required Packages property.
- Navigate to the CDSW service.
- Click Configuration.
- Search for the Install Required Packages property. If this property is enabled, you can move on to the next step and run Prepare Node.
However, if the property has been disabled, you must either enable it or manually install the following packages on all Cloudera Data Science Workbench gateway hosts.
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 conntrack-tools socat
Run the Prepare Node command.
- In Cloudera Manager, navigate to the Cloudera Data Science Workbench service.
- Click the Instances tab.
- Use the checkboxes to select all host instances and click Actions for Selected (x).
- Click Prepare Node. Once again, click Prepare Node to confirm the action.
- Log into the Cloudera Manager Admin Console and restart the Cloudera Data Science Workbench service.
- On the Restart from the dropdown. tab, click to the right of the CDSW service and select
- Confirm your choice on the next screen. Note that a complete restart of the service will take time. Even though the CDSW service status shows Good Health, the application itself will take some more time to get ready.
- Upgrade Projects to Use the Latest Base Engine Images
If the release you have just upgraded to includes a new version of the base engine image (see release notes), you will need to manually configure existing projects to use the new engine. Cloudera recommends you do so to take advantage of any new features and bug fixes included in the newly released engine. For example:
- Container Security
Security best practices dictate that engine containers should not run as the root user. Engines (v7 and lower) briefly initialize as the root user and then run as the cdsw user. Engines v8 (and higher) now follow the best practice and run only as the cdsw user. For more details, see Restricting User-Created Pods.
- CDH 6 Compatibility
The base engine image you use must be compatible with the version of CDH you are running. This is especially important if you are running workloads on Spark. Older base engines (v6 and lower) cannot support the latest versions of CDH 6. If you want to run Spark workloads on CDH 6, you must upgrade your projects to base engine 7 (or higher).
Engines v8 (and higher) ships with the browser-based IDE, Jupyter, preconfigured and can be selected from the Start Session menu.
To upgrade a project to the new engine, go to the project's extended engines, you will need to modify them to use the new base engine image.page and select the new engine from the dropdown. If any of your projects are using custom
- Container Security
- (GPU-enabled Deployments) Remove nvidia-docker1 and Upgrade NVIDIA Drivers to 410.xx or higher
Perform the following steps to make sure you can continue to leverage GPUs for workloads on Cloudera Data Science Workbench 1.6 (and higher).
Remove nvidia-docker1. Cloudera Data Science Workbench (version 1.6 and higher) ships with nvidia-docker2 installed by default.
yum remove nvidia-dockerPerform this step on all hosts that have GPUs attached to them.
Upgrade your NVIDIA driver to version 410.xx (or higher). This must be done because nvidia-docker2 does not support lower versions of NVIDIA drivers.
- Stop Cloudera Data Science Workbench.
Depending on your deployment, either stop the CDSW service in Cloudera Manager (for CSDs) or run cdsw stop on the Master host (for RPMs).
- Reboot the GPU-enabled hosts.
- Install a supported version of the NVIDIA driver (410.xx or higher) on all GPU-enabled hosts.
- Start Cloudera Data Science Workbench.
Depending on your deployment, either start the CDSW service in Cloudera Manager (for CSDs) or run cdsw start on the Master host (for RPMs).
- Stop Cloudera Data Science Workbench.