Dataproc은 Compute Engine 리전을 기반으로 리전 엔드포인트를 지원합니다.
Dataproc 클러스터를 만들 때 'us-east1' 또는 'europe-west1'과 같은 리전을 지정해야 합니다. Dataproc은 지정된 리전 내 영역 내에서 VM 인스턴스, Cloud Storage와 같은 클러스터 리소스와 메타데이터 스토리지를 격리합니다.
필요에 따라 클러스터를 만들 때 지정된 클러스터 리전 내에서 'us-east1-a' 또는 'europe-west1-b'와 같은 영역을 지정할 수 있습니다. 영역을 지정하지 않으면 Dataproc 자동 영역 배치가 지정된 클러스터 리전 내에서 클러스터 리소스를 찾을 영역을 선택합니다.
리전 엔드포인트 이름은 Compute Engine 리전을 기반으로 표준 명명 규칙을 따릅니다.
예를 들어 미국 중부 리전의 이름은 us-central1이고 서유럽 리전의 이름은 europe-west1입니다. gcloud compute regions list 명령어를 실행하면 사용 가능한 리전의 목록을 확인할 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-26(UTC)"],[[["\u003cp\u003eDataproc clusters must be created within a specified Compute Engine region, such as "us-east1" or "europe-west1," to isolate cluster resources within a zone of that region.\u003c/p\u003e\n"],["\u003cp\u003eYou can optionally specify a zone within the chosen region, or if not, Dataproc Auto Zone Placement will automatically select one.\u003c/p\u003e\n"],["\u003cp\u003eRegional endpoint names follow a standard convention based on Compute Engine regions, for example, "us-central1" for Central US and "europe-west1" for Western Europe.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating a cluster via gcloud, REST API, gRPC, or the Google Cloud console, you must specify the desired region.\u003c/p\u003e\n"],["\u003cp\u003eRegional endpoints for gRPC clients can be specified with this pattern: \u003ccode\u003e<var translate="no">REGION</var>\u003c/code\u003e-dataproc.googleapis.com.\u003c/p\u003e\n"]]],[],null,["Dataproc supports regional endpoints based on\n[Compute Engine regions](/compute/docs/regions-zones#available).\nYou must specify a region, such as \"us-east1\" or \"europe-west1\",\nwhen you create a Dataproc cluster. Dataproc\nwill isolate cluster resources, such as VM instances and Cloud Storage\nand metadata storage, within a zone within the specified region.\n\nYou can optionally specify a zone within the specified cluster region, such as\n\"us-east1-a\" or \"europe-west1-b\", when you create a cluster. If you do not\nspecify the zone, [Dataproc Auto Zone Placement](/dataproc/docs/concepts/auto-zone)\nwill choose a zone within your specified cluster region to locate clusters\nresources.\n\nThe regional namespace corresponds to the `/regions/`\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\nsegment of Dataproc resource URIs (see, for example, the\ncluster\n[`networkUri`](/dataproc/docs/reference/rest/v1/ClusterConfig#GceClusterConfig.FIELDS.network_uri)).\n\nRegional endpoint semantics\n\nRegional endpoint names follow a standard naming convention based on\n[Compute Engine regions](/compute/docs/regions-zones/regions-zones#available).\nFor example, the name for the Central US region is `us-central1`, and the name\nof the Western Europe region is `europe-west1`. Run the `gcloud compute regions list`\ncommand to see a listing of available regions.\n| **Note:** When new regions are added to Compute Engine, they become available for use with Dataproc.\n\nCreate a cluster \n\ngcloud\n\nWhen you create a cluster, specify a region using the required\n`--region` flag. \n\n```\ngcloud dataproc clusters create CLUSTER_NAME \\\n --region=REGION \\\n other args ...\n```\n\nREST API\n\nUse the `REGION` URL parameter in a\n[clusters.create](/dataproc/docs/reference/rest/v1/projects.regions.clusters/create)\nrequest to specify the cluster region.\n\ngRPC\n\nSet the client transport address to the regional endpoint\nusing the following pattern:\n\n\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e`-dataproc.googleapis.com`\n\n**Python ([google-cloud-python](https://github.com/googleapis/python-dataproc)) example:** \n\n```python\nfrom google.cloud import dataproc_v1\nfrom google.cloud.dataproc_v1.gapic.transports import cluster_controller_grpc_transport\n\ntransport = cluster_controller_grpc_transport.ClusterControllerGrpcTransport(\n address='us-central1-dataproc.googleapis.com:443')\nclient = dataproc_v1.ClusterControllerClient(transport)\n\nproject_id = 'my-project'\nregion = 'us-central1'\ncluster = {...}\n```\n\n**Java ([google-cloud-java](https://github.com/googleapis/google-cloud-java/tree/master/google-cloud-clients/google-cloud-dataproc)) example:** \n\n```verilog\nClusterControllerSettings settings =\n ClusterControllerSettings.newBuilder()\n .setEndpoint(\"us-central1-dataproc.googleapis.com:443\")\n .build();\n try (ClusterControllerClient clusterControllerClient = ClusterControllerClient.create(settings)) {\n String projectId = \"my-project\";\n String region = \"us-central1\";\n Cluster cluster = Cluster.newBuilder().build();\n Cluster response =\n clusterControllerClient.createClusterAsync(projectId, region, cluster).get();\n }\n```\n\nConsole\n\nSpecify a Dataproc region in the Location section of the\n**Set up cluster** panel on the Dataproc\n[**Create a cluster**](https://console.cloud.google.com/dataproc/clustersAdd) page\nin the Google Cloud console.\n\n\nWhat's next\n\n- [Geography and Regions](/docs/geography-and-regions)\n- [Compute Engine Engine→Regions and Zones](/compute/docs/regions-zones/regions-zones)\n- [Compute Engine→Global, Regional, and Zonal Resources](/compute/docs/regions-zones/global-regional-zonal-resources)\n- [Dataproc Auto Zone Placement](/dataproc/docs/concepts/auto-zone)"]]