Faster machine learning on Dataproc with new initialization action
Apache Hadoop and Apache Spark are established and standard frameworks for distributed storage and data processing. Google Cloud’s Dataproc is a fast, easy-to-use, fully managed cloud service for running Apache Spark and Apache Hadoop clusters in a simple, cost-efficient way. For users looking to build machine learning models, you might use Dataproc for preprocessing your data using Apache Spark and then use that same Spark cluster to power your Notebook for machine learning. We created the machine learning initialization action to provide a set of commonly-used libraries to reduce the time spent configuring your cluster for machine learning.
In this blog, you will learn how you can get started working with this initialization action on a Dataproc cluster. This will provide you with an environment that lets you leverage the latest and greatest in open source machine learning, including:
RAPIDS on Spark (optionally)
GPUs and drivers (optionally)
The machine learning initialization action relies on using other initialization actions for installing certain components, such as RAPIDS, Dask and GPU drivers. As such, you have access to the full functionality and configurations that these components provide.
Data preprocessing and machine learning training in one place
The machine learning initialization action for Dataproc provides a environment for running production Spark, Dask or other ETL jobs on your data while also being able to build your machine learning models with your choice of machine learning libraries, all in the same place. By adding GPUs to your cluster configuration, you can also decrease the training time for machine learning models with TensorFlow or RAPIDS, as well as use the RAPIDS SQL Accelerator to further improve the efficiencies of model training.
Configure your Google Cloud Platform project
You’ll need a Google Cloud Platform (GCP) project. Use your own or create a new one following the instructions here.
The machine learning initialization action relies on using other initialization actions for parts of its installation. You can make a copy of these scripts to effectively “pin” the versions of the scripts that you’re using. To do so, create a Cloud Storage bucket, and copy the scripts into this bucket.
Create a Dataproc cluster with the machine learning initialization action
You’ll now proceed with the creation of your cluster. First, define a region and a cluster name.
Next, run the following command. This will create a cluster configured with the machine learning initialization action configured. The cluster will contain 1 master node, 2 worker nodes and 2 NVIDIA T4 GPUs available to each node. The cluster’s Jupyter optional component will also be enabled along with component gateway to access the cluster using Jupyter Notebooks or JupyterLab.
The configuration shown above will create a Dataproc cluster equipped with NVIDIA graphics cards and their respective drivers installed. You can then take advantage of GPU-accelerated data processing using frameworks such as NVIDIA RAPIDS or TensorFlow.
In this configuration, we’re including the `init-actions-repo` metadata flag to tell the machine learning initialization action where to locate the necessary other installation scripts. Additionally, we’re including the `include-gpus=true` and `gpu-driver-provider=NVIDIA` flags to tell the script that we want to install GPU drivers and that the drivers should come from NVIDIA. You can optionally run the cluster without any GPUs attached or drivers included.
Alternatively, you can also equip the cluster with NVIDIA RAPIDS Spark Jars, or NVIDIA RAPIDS for Dask. You can do so with the `rapids-runtime` metadata flag and assign this to be DASK or RAPIDS.
Use the spark-tensorflow-distributor to run distributed TensorFlow jobs
You can run distributed TensorFlow jobs on your Spark cluster with the spark-tensorflow-distributor included in the machine learning initialization action. This library is a wrapper for the TensorFlow distributed library. Copy the following code into a file `spark_tf_dist.py`.
This code uses the MirroredStrategyRunner to submit a TensorFlow training job to your Spark cluster. The Spark config provided will ensure your cluster is able to best utilize the GPUs on your cluster for training.
You can then submit a TensorFlow code as a PySpark job to your cluster:
The machine learning initialization action is great to use in a notebook environment. One way to do this is using the Jupyter Optional Componentwith Dataproc, and more information for this can be found in this blog post. Another excellent way is to use Dataproc Hub, Dataproc’s managed JupyterLab service. This service allows IT administrators to provide preconfigured environments optimized for security and resources allocation to their data scientists while giving the data scientists the flexibility to customize the packages and libraries available on the cluster. You can configure your cluster with the machine learning initialization action by following the instructions here and using the following YAML configuration:
For more Information on Dataproc Hub, check out this announcement blog.
The machine learning initialization action is a great place to run both your ETL processing jobs as well as train machine learning models. You can also customize your experience with any of our other open source initialization actions. Additionally, you can create a custom Dataproc image for convenience and faster cluster creation times. For more information on getting started with the machine learning initialization action, check out the documentation here. You can also get started using Dask on Dataproc with Google Cloud Platform’s $300 credit for new customers.
Related Google News:
- Migrating Apache Hadoop to Dataproc: A decision tree February 23, 2021
- Run Data Science at Scale with Dataproc and Apache Spark February 23, 2021
- Your Android is now even safer — and 5 other new features February 23, 2021
- New Password Checkup Feature Coming to Android February 23, 2021
- Our all-new TalkBack screen reader February 23, 2021
- Improvements for locating new comments and important conversations in Google Docs February 22, 2021
- New Association functionality added to Search Console February 22, 2021
- New option to download third-party apps and domain wide delegation to CSV February 18, 2021