gcloud_dataproc_jobs_submit_hadoop (1)
NAME
- gcloud dataproc jobs submit hadoop - submit a Hadoop job to a cluster
SYNOPSIS
-
gcloud dataproc jobs submit hadoop --cluster=CLUSTER (--class=MAIN_CLASS | --jar=MAIN_JAR) [--archives=[ARCHIVE,...]] [--async] [--bucket=BUCKET] [--driver-log-levels=[PACKAGE=LEVEL,...]] [--files=[FILE,...]] [--jars=[JAR,...]] [--labels=[KEY=VALUE,...]] [--max-failures-per-hour=MAX_FAILURES_PER_HOUR] [--properties=[PROPERTY=VALUE,...]] [--region=REGION] [GCLOUD_WIDE_FLAG ...] [-- JOB_ARGS ...]
DESCRIPTION
POSITIONAL ARGUMENTS
-
- [-- JOB_ARGS ...]
-
The arguments to pass to the driver.
The '--' argument must be specified between gcloud specific args on the left and JOB_ARGS on the right.
REQUIRED FLAGS
-
- --cluster=CLUSTER
-
The Dataproc cluster to submit the job to.
-
Exactly one of these must be specified:
-
- --class=MAIN_CLASS
-
The class containing the main method of the driver. Must be in a provided jar or
jar that is already on the classpath
- --jar=MAIN_JAR
-
The HCFS URI of jar file containing the driver jar.
-
OPTIONAL FLAGS
-
- --archives=[ARCHIVE,...]
-
Comma separated list of archives to be provided to the job. must be one of the
following file formats: .zip, .tar, .tar.gz, or .tgz.
- --async
-
Does not wait for the job to run.
- --bucket=BUCKET
-
The Cloud Storage bucket to stage files in. Defaults to the cluster's configured
bucket.
- --driver-log-levels=[PACKAGE=LEVEL,...]
-
A list of package to log4j log level pairs to configure driver logging. For
example: root=FATAL,com.example=INFO
- --files=[FILE,...]
-
Comma separated list of files to be provided to the job.
- --jars=[JAR,...]
-
Comma separated list of jar files to be provided to the MR and driver
classpaths.
- --labels=[KEY=VALUE,...]
-
List of label KEY=VALUE pairs to add.
Keys must start with a lowercase character and contain only hyphens (-), underscores (_), lowercase characters, and numbers. Values must contain only hyphens (-), underscores (_), lowercase characters, and numbers.
- --max-failures-per-hour=MAX_FAILURES_PER_HOUR
-
Specifies maximum number of times a job can be restarted in event of failure.
Expressed as a per-hour rate. Default is 0 (no failure retries).
- --properties=[PROPERTY=VALUE,...]
-
A list of key value pairs to configure Hadoop.
- --region=REGION
-
Cloud Dataproc region to use. Each Cloud Dataproc region constitutes an
independent resource namespace constrained to deploying instances into Compute
Engine zones inside the region. The default value of global is a special
multi-region namespace which is capable of deploying instances into all Compute
Engine zones globally, and is disjoint from other Cloud Dataproc regions.
Overrides the default dataproc/region property value for this command
invocation.
GCLOUD WIDE FLAGS
These flags are available to all commands: --account, --configuration, --flags-file, --flatten, --format, --help, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details.
EXAMPLES
To submit a Hadoop job that runs the main class of a jar, run:
-
$ gcloud dataproc jobs submit hadoop --cluster my_cluster \
--jar my_jar.jar -- arg1 arg2
To submit a Hadoop job that runs a specific class of a jar, run:
-
$ gcloud dataproc jobs submit hadoop --cluster my_cluster \
--class org.my.main.Class \
--jars my_jar1.jar,my_jar2.jar -- arg1 arg2
To submit a Hadoop job that runs a jar that is already on the cluster, run:
-
$ gcloud dataproc jobs submit hadoop --cluster my_cluster \
--jar file:///usr/lib/hadoop-op/hadoop-op-examples.jar \
-- wordcount gs://my_bucket/my_file.txt gs://my_bucket/output
NOTES
These variants are also available:
- $ gcloud alpha dataproc jobs submit hadoop $ gcloud beta dataproc jobs submit hadoop