gcloud beta dataproc clusters list Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud beta dataproc clusters list - view a list of clusters in a project
- SYNOPSIS
gcloud beta dataproc clusters list[--region=REGION][--filter=EXPRESSION][--limit=LIMIT][--page-size=PAGE_SIZE; default=100][--sort-by=[FIELD,…]][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
(BETA)View a list of clusters in a project. An optional filter canbe used to constrain the clusters returned. Filters are case-sensitive and havethe following syntax:field=value[AND[field=value]]…
where
fieldis one ofstatus.state,clusterName, orlabels.[KEY], and[KEY]is a label key.valuecan be*to match all values.status.statecan be one of the following:ACTIVE,INACTIVE,CREATING,RUNNING,ERROR,DELETING, orUPDATING.ACTIVEcontains theCREATING,UPDATING,andRUNNINGstates.INACTIVEcontains theDELETINGandERRORstates.clusterNameisthe name of the cluster provided at creation time. Only the logicalANDoperator is supported; space-separated items are treated ashaving an implicitANDoperator.- EXAMPLES
- To see the list of all clusters in Dataproc's 'us-central1' region, run:
gcloudbetadataprocclusterslist--region='us-central1'To show a cluster in Dataproc's 'global' region with the name 'mycluster', run:
gcloudbetadataprocclusterslist--region='global'--filter='clusterName = mycluster'To see the list of all clusters in Dataproc's 'global' region with specifiedlabels, run:
gcloudbetadataprocclusterslist--region='global'--filter='labels.env = staging ANDlabels.starred = *'To see a list of all active clusters in Dataproc's 'europe-west1' region withspecified labels, run:
gcloudbetadataprocclusterslist--region='europe-west1'--filter='status.state = ACTIVE ANDlabels.env = staging AND labels.starred = *' - FLAGS
--region=REGION- Dataproc region to use. Each Dataproc region constitutes an independent resourcenamespace constrained to deploying instances into Compute Engine zones insidethe region. Overrides the default
dataproc/regionproperty valuefor this command invocation.
- LIST COMMAND FLAGS
--filter=EXPRESSION- Apply a Boolean filter
EXPRESSIONto each resource itemto be listed. If the expression evaluatesTrue, then that item islisted. For more details and examples of filter expressions, run $gcloud topic filters. This flaginteracts with other flags that are applied in this order:--flatten,--sort-by,--filter,--limit. --limit=LIMIT- Maximum number of resources to list. The default is
unlimited. Thisflag interacts with other flags that are applied in this order:--flatten,--sort-by,--filter,--limit. --page-size=PAGE_SIZE; default=100- Some services group resource list output into pages. This flag specifies themaximum number of resources per page. The default is
100. Pagingmay be applied before or after--filterand--limitdepending on the service. --sort-by=[FIELD,…]- Comma-separated list of resource field key names to sort by. The default orderis ascending. Prefix a field with ``~´´ for descending order on thatfield. This flag interacts with other flags that are applied in this order:
--flatten,--sort-by,--filter,--limit.
- GCLOUD WIDE FLAGS
- These flags are available to all commands:
--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.Run
$gcloud helpfor details. - NOTES
- This command is currently in beta and might change without notice. Thesevariants are also available:
gclouddataprocclusterslistgcloudalphadataprocclusterslist
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-22 UTC.