How to execute individual steps on Spark
spark
integration brings two different step operators:
SparkStepOperator
serves as the base class for all the Spark-related step operators.
KubernetesSparkStepOperator
is responsible for launching ZenML steps as Spark applications with Kubernetes as a cluster manager.
SparkStepOperator
master
is the master URL for the cluster where Spark will run. You might see different schemes for this URL with varying cluster managers such as Mesos, YARN, or Kubernetes.
deploy_mode
can either be ‘cluster’ (default) or ‘client’ and it decides where the driver node of the application will run.
submit_args
is the JSON string of a dictionary, which will be used to define additional params if required (Spark has a wide variety of parameters, thus including them all in a single class was deemed unnecessary.).
launch
method of the step operator gets additional configuration parameters from the DockerSettings
and ResourceSettings
. As a result, the overall configuration happens in 4 base methods:
_resource_configuration
translates the ZenML ResourceSettings
object to Spark’s own resource configuration.
_backend_configuration
is responsible for cluster-manager-specific configuration.
_io_configuration
is a critical method. Even though we have materializers, Spark might require additional packages and configuration to work with a specific filesystem. This method is used as an interface to provide this configuration.
_additional_configuration
takes the submit_args
, converts, and appends them to the overall configuration.
_launch_spark_job
comes into play. This takes the completed configuration and runs a Spark job on the given master
URL with the specified deploy_mode
. By default, this is achieved by creating and executing a spark-submit
command.
_io_configuration
method is only effective when it is paired with an S3ArtifactStore
(which has an authentication secret). When used with other artifact store flavors, you might be required to provide additional configuration through the submit_args
.
KubernetesSparkStepOperator
KubernetesSparkStepOperator
is implemented by subclassing the base SparkStepOperator
and uses the PipelineDockerImageBuilder
class to build and push the required docker images.
namespace
is the namespace under which the driver and executor pods will run.
service_account
is the service account that will be used by various Spark components (to create and watch the pods).
_backend_configuration
method is adjusted to handle the Kubernetes-specific configuration.
KubernetesSparkStepOperator
requires a Kubernetes cluster in order to run. There are many ways to deploy a Kubernetes cluster using different cloud providers or on your custom infrastructure, and we can’t possibly cover all of them, but you can check out the spark example to see how it is deployed on AWS.
KubernetesSparkStepOperator
, you need:
spark
integration. If you haven’t installed it already, run@step
decorator as follows:
SparkStepOperatorSettings
when defining or running your pipeline. Check out the API docs for a full list of available attributes and this docs page for more information on how to specify settings.
A concrete example of using the Spark step operator can be found here.