mirror of
https://github.com/OMGeeky/google-apis-rs.git
synced 2026-02-23 15:49:49 +01:00
Update documentation
This commit is contained in:
Sebastian Thiel
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Regions Clusters Patch - Dataproc v2.0.4+20210322</title>
|
||||
<title>Regions Clusters Patch - Dataproc v3.0.0+20220224</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Dataproc v2.0.4+20210322</a>
|
||||
<a href=".." class="icon icon-home"> Dataproc v3.0.0+20220224</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -84,6 +84,26 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_locations-batches-create">Locations Batches Create</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_locations-batches-delete">Locations Batches Delete</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_locations-batches-get">Locations Batches Get</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_locations-batches-list">Locations Batches List</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_locations-workflow-templates-create">Locations Workflow Templates Create</a>
|
||||
|
||||
@@ -238,6 +258,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_regions-clusters-repair">Regions Clusters Repair</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_regions-clusters-set-iam-policy">Regions Clusters Set Iam Policy</a>
|
||||
|
||||
@@ -429,7 +454,7 @@
|
||||
</div>
|
||||
<div role="main">
|
||||
<div class="section">
|
||||
<p>Updates a cluster in a project. The returned Operation.metadata will be ClusterOperationMetadata (https://cloud.google.com/dataproc/docs/reference/rpc/google.cloud.dataproc.v1#clusteroperationmetadata).</p>
|
||||
<p>Updates a cluster in a project. The returned Operation.metadata will be ClusterOperationMetadata (https://cloud.google.com/dataproc/docs/reference/rpc/google.cloud.dataproc.v1#clusteroperationmetadata). The cluster must be in a RUNNING state or an error is returned.</p>
|
||||
<h1 id="scopes">Scopes</h1>
|
||||
<p>You will need authorization for the <em>https://www.googleapis.com/auth/cloud-platform</em> scope to make a valid call.</p>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/cloud-platform</em>.
|
||||
@@ -466,6 +491,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
enable-http-port-access: boolean
|
||||
http-ports: { string: string }
|
||||
gce-cluster-config:
|
||||
confidential-instance-config:
|
||||
enable-confidential-compute: boolean
|
||||
internal-ip-only: boolean
|
||||
metadata: { string: string }
|
||||
network-uri: string
|
||||
@@ -498,6 +525,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
disk-config:
|
||||
boot-disk-size-gb: integer
|
||||
boot-disk-type: string
|
||||
local-ssd-interface: string
|
||||
num-local-ssds: integer
|
||||
image-uri: string
|
||||
instance-names: [string]
|
||||
@@ -515,6 +543,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
disk-config:
|
||||
boot-disk-size-gb: integer
|
||||
boot-disk-type: string
|
||||
local-ssd-interface: string
|
||||
num-local-ssds: integer
|
||||
image-uri: string
|
||||
instance-names: [string]
|
||||
@@ -554,6 +583,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
disk-config:
|
||||
boot-disk-size-gb: integer
|
||||
boot-disk-type: string
|
||||
local-ssd-interface: string
|
||||
num-local-ssds: integer
|
||||
image-uri: string
|
||||
instance-names: [string]
|
||||
@@ -580,94 +610,100 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . cluster-name=aliquyam</code><ul>
|
||||
<li><code>-r . cluster-name=at</code><ul>
|
||||
<li>Required. The cluster name. Cluster names within a project must be unique. Names of deleted clusters can be reused.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>cluster-uuid=sanctus</code><ul>
|
||||
<li><code>cluster-uuid=at</code><ul>
|
||||
<li>Output only. A cluster UUID (Unique Universal Identifier). Dataproc generates this value when it creates the cluster.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>config.autoscaling-config policy-uri=invidunt</code></p>
|
||||
<p><code>config.autoscaling-config policy-uri=kasd</code></p>
|
||||
<ul>
|
||||
<li>Optional. The autoscaling policy used by the cluster.Only resource names including projectid and location (region) are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/locations/[dataproc_region]/autoscalingPolicies/[policy_id] projects/[project_id]/locations/[dataproc_region]/autoscalingPolicies/[policy_id]Note that the policy must be in the same project and Dataproc region.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. config-bucket=dolor</code></p>
|
||||
<p><code>.. config-bucket=magna</code></p>
|
||||
<ul>
|
||||
<li>Optional. A Cloud Storage bucket used to stage job dependencies, config files, and job driver console output. If you do not specify a staging bucket, Cloud Dataproc will determine a Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Compute Engine zone where your cluster is deployed, and then create and manage this project-level, per-location bucket (see Dataproc staging bucket (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/staging-bucket)). This field requires a Cloud Storage bucket name, not a URI to a Cloud Storage bucket.</li>
|
||||
<li>Optional. A Cloud Storage bucket used to stage job dependencies, config files, and job driver console output. If you do not specify a staging bucket, Cloud Dataproc will determine a Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Compute Engine zone where your cluster is deployed, and then create and manage this project-level, per-location bucket (see Dataproc staging and temp buckets (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/staging-bucket)). This field requires a Cloud Storage bucket name, not a gs://... URI to a Cloud Storage bucket.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>encryption-config gce-pd-kms-key-name=eos</code></p>
|
||||
<p><code>encryption-config gce-pd-kms-key-name=amet.</code></p>
|
||||
<ul>
|
||||
<li>Optional. The Cloud KMS key name to use for PD disk encryption for all instances in the cluster.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..endpoint-config enable-http-port-access=false</code></p>
|
||||
<p><code>..endpoint-config enable-http-port-access=true</code></p>
|
||||
<ul>
|
||||
<li>Optional. If true, enable http access to specific ports on the cluster from external sources. Defaults to false.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>http-ports=key=no</code></p>
|
||||
<p><code>http-ports=key=eos</code></p>
|
||||
<ul>
|
||||
<li>Output only. The map of port descriptions to URLs. Will only be populated if enable_http_port_access is true.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..gce-cluster-config internal-ip-only=false</code></p>
|
||||
<p><code>..gce-cluster-config.confidential-instance-config enable-confidential-compute=true</code></p>
|
||||
<ul>
|
||||
<li>Optional. Defines whether the instance should have confidential compute enabled.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. internal-ip-only=true</code></p>
|
||||
<ul>
|
||||
<li>Optional. If true, all instances in the cluster will only have internal IP addresses. By default, clusters are not restricted to internal IP addresses, and will have ephemeral external IP addresses assigned to each instance. This internal_ip_only restriction can only be enabled for subnetwork enabled networks, and all off-cluster dependencies must be configured to be accessible without external IP addresses.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>metadata=key=aliquyam</code><ul>
|
||||
<li><code>metadata=key=diam</code><ul>
|
||||
<li>The Compute Engine metadata entries to add to all instances (see Project and instance metadata (https://cloud.google.com/compute/docs/storing-retrieving-metadata#project_and_instance_metadata)).</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>network-uri=consetetur</code><ul>
|
||||
<li><code>network-uri=elitr</code><ul>
|
||||
<li>Optional. The Compute Engine network to be used for machine communications. Cannot be specified with subnetwork_uri. If neither network_uri nor subnetwork_uri is specified, the "default" network of the project is used, if it exists. Cannot be a "Custom Subnet Network" (see Using Subnetworks (https://cloud.google.com/compute/docs/subnetworks) for more information).A full URL, partial URI, or short name are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/global/default projects/[project_id]/regions/global/default default</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>node-group-affinity node-group-uri=ea</code></p>
|
||||
<p><code>node-group-affinity node-group-uri=sea</code></p>
|
||||
<ul>
|
||||
<li>Required. The URI of a sole-tenant node group resource (https://cloud.google.com/compute/docs/reference/rest/v1/nodeGroups) that the cluster will be created on.A full URL, partial URI, or node group name are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-central1-a/nodeGroups/node-group-1 projects/[project_id]/zones/us-central1-a/nodeGroups/node-group-1 node-group-1</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. private-ipv6-google-access=lorem</code></p>
|
||||
<p><code>.. private-ipv6-google-access=vero</code></p>
|
||||
<ul>
|
||||
<li>Optional. The type of IPv6 access for a cluster.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>reservation-affinity consume-reservation-type=elitr</code><ul>
|
||||
<li><code>reservation-affinity consume-reservation-type=et</code><ul>
|
||||
<li>Optional. Type of reservation to consume</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>key=justo</code><ul>
|
||||
<li><code>key=lorem</code><ul>
|
||||
<li>Optional. Corresponds to the label key of reservation resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>values=lorem</code></p>
|
||||
<p><code>values=sit</code></p>
|
||||
<ul>
|
||||
<li>Optional. Corresponds to the label values of reservation resource.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. service-account=labore</code></p>
|
||||
<p><code>.. service-account=lorem</code></p>
|
||||
<ul>
|
||||
<li>Optional. The Dataproc service account (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/service-accounts#service_accounts_in_dataproc) (also see VM Data Plane identity (https://cloud.google.com/dataproc/docs/concepts/iam/dataproc-principals#vm_service_account_data_plane_identity)) used by Dataproc cluster VM instances to access Google Cloud Platform services.If not specified, the Compute Engine default service account (https://cloud.google.com/compute/docs/access/service-accounts#default_service_account) is used.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>service-account-scopes=gubergren</code><ul>
|
||||
<li><code>service-account-scopes=amet.</code><ul>
|
||||
<li>Optional. The URIs of service account scopes to be included in Compute Engine instances. The following base set of scopes is always included: https://www.googleapis.com/auth/cloud.useraccounts.readonly https://www.googleapis.com/auth/devstorage.read_write https://www.googleapis.com/auth/logging.writeIf no scopes are specified, the following defaults are also provided: https://www.googleapis.com/auth/bigquery https://www.googleapis.com/auth/bigtable.admin.table https://www.googleapis.com/auth/bigtable.data https://www.googleapis.com/auth/devstorage.full_control</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
@@ -687,66 +723,70 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. subnetwork-uri=et</code></p>
|
||||
<p><code>.. subnetwork-uri=takimata</code></p>
|
||||
<ul>
|
||||
<li>Optional. The Compute Engine subnetwork to be used for machine communications. Cannot be specified with network_uri.A full URL, partial URI, or short name are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/us-east1/subnetworks/sub0 projects/[project_id]/regions/us-east1/subnetworks/sub0 sub0</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>tags=dolore</code><ul>
|
||||
<li><code>tags=et</code><ul>
|
||||
<li>The Compute Engine tags to add to all instances (see Tagging instances (https://cloud.google.com/compute/docs/label-or-tag-resources#tags)).</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>zone-uri=voluptua.</code></p>
|
||||
<p><code>zone-uri=dolores</code></p>
|
||||
<ul>
|
||||
<li>Optional. The zone where the Compute Engine cluster will be located. On a create request, it is required in the "global" region. If omitted in a non-global Dataproc region, the service will pick a zone in the corresponding Compute Engine region. On a get request, zone will always be present.A full URL, partial URI, or short name are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/[zone] projects/[project_id]/zones/[zone] us-central1-f</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..gke-cluster-config.namespaced-gke-deployment-target cluster-namespace=sit</code></p>
|
||||
<p><code>..gke-cluster-config.namespaced-gke-deployment-target cluster-namespace=dolores</code></p>
|
||||
<ul>
|
||||
<li>Optional. A namespace within the GKE cluster to deploy into.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>target-gke-cluster=sanctus</code></p>
|
||||
<p><code>target-gke-cluster=diam</code></p>
|
||||
<ul>
|
||||
<li>Optional. The target GKE cluster to deploy to. Format: 'projects/{project}/locations/{location}/clusters/{cluster_id}'</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>...lifecycle-config auto-delete-time=ipsum</code></p>
|
||||
<p><code>...lifecycle-config auto-delete-time=ea</code></p>
|
||||
<ul>
|
||||
<li>Optional. The time when cluster will be auto-deleted (see JSON representation of Timestamp (https://developers.google.com/protocol-buffers/docs/proto3#json)).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>auto-delete-ttl=eirmod</code><ul>
|
||||
<li><code>auto-delete-ttl=sea</code><ul>
|
||||
<li>Optional. The lifetime duration of cluster. The cluster will be auto-deleted at the end of this period. Minimum value is 10 minutes; maximum value is 14 days (see JSON representation of Duration (https://developers.google.com/protocol-buffers/docs/proto3#json)).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>idle-delete-ttl=vero</code><ul>
|
||||
<li><code>idle-delete-ttl=dolore</code><ul>
|
||||
<li>Optional. The duration to keep the cluster alive while idling (when no jobs are running). Passing this threshold will cause the cluster to be deleted. Minimum value is 5 minutes; maximum value is 14 days (see JSON representation of Duration (https://developers.google.com/protocol-buffers/docs/proto3#json)).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>idle-start-time=voluptua.</code></p>
|
||||
<p><code>idle-start-time=dolores</code></p>
|
||||
<ul>
|
||||
<li>Output only. The time when cluster became idle (most recent job finished) and became eligible for deletion due to idleness (see JSON representation of Timestamp (https://developers.google.com/protocol-buffers/docs/proto3#json)).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..master-config.disk-config boot-disk-size-gb=91</code></p>
|
||||
<p><code>..master-config.disk-config boot-disk-size-gb=13</code></p>
|
||||
<ul>
|
||||
<li>Optional. Size in GB of the boot disk (default is 500GB).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>boot-disk-type=ipsum</code><ul>
|
||||
<li><code>boot-disk-type=tempor</code><ul>
|
||||
<li>Optional. Type of the boot disk (default is "pd-standard"). Valid values: "pd-balanced" (Persistent Disk Balanced Solid State Drive), "pd-ssd" (Persistent Disk Solid State Drive), or "pd-standard" (Persistent Disk Hard Disk Drive). See Disk types (https://cloud.google.com/compute/docs/disks#disk-types).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>local-ssd-interface=et</code><ul>
|
||||
<li>Optional. Interface type of local SSDs (default is "scsi"). Valid values: "scsi" (Small Computer System Interface), "nvme" (Non-Volatile Memory Express). See local SSD performance (https://cloud.google.com/compute/docs/disks/local-ssd#performance).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>num-local-ssds=91</code></p>
|
||||
<p><code>num-local-ssds=23</code></p>
|
||||
<ul>
|
||||
<li>Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.</li>
|
||||
</ul>
|
||||
@@ -757,74 +797,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Optional. The Compute Engine image resource used for cluster instances.The URI can represent an image or image family.Image examples: https://www.googleapis.com/compute/beta/projects/[project_id]/global/images/[image-id] projects/[project_id]/global/images/[image-id] image-idImage family examples. Dataproc will use the most recent image from the family: https://www.googleapis.com/compute/beta/projects/[project_id]/global/images/family/[custom-image-family-name] projects/[project_id]/global/images/family/[custom-image-family-name]If the URI is unspecified, it will be inferred from SoftwareConfig.image_version or the system default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>instance-names=gubergren</code><ul>
|
||||
<li>Output only. The list of instance names. Dataproc derives the names from cluster_name, num_instances, and the instance group.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>is-preemptible=false</code><ul>
|
||||
<li>Output only. Specifies that this instance group contains preemptible instances.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>machine-type-uri=takimata</code><ul>
|
||||
<li>Optional. The Compute Engine machine type used for cluster instances.A full URL, partial URI, or short name are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2 projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2 n1-standard-2Auto Zone Exception: If you are using the Dataproc Auto Zone Placement (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone#using_auto_zone_placement) feature, you must use the short name of the machine type resource, for example, n1-standard-2.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>managed-group-config instance-group-manager-name=duo</code><ul>
|
||||
<li>Output only. The name of the Instance Group Manager for this group.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>instance-template-name=tempor</code></p>
|
||||
<ul>
|
||||
<li>Output only. The name of the Instance Template used for the Managed Instance Group.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. min-cpu-platform=clita</code></p>
|
||||
<ul>
|
||||
<li>Optional. Specifies the minimum cpu platform for the Instance Group. See Dataproc -> Minimum CPU Platform (https://cloud.google.com/dataproc/docs/concepts/compute/dataproc-min-cpu).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-instances=71</code><ul>
|
||||
<li>Optional. The number of VM instances in the instance group. For HA cluster master_config groups, must be set to 3. For standard cluster master_config groups, must be set to 1.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>preemptibility=no</code></p>
|
||||
<ul>
|
||||
<li>Optional. Specifies the preemptibility of the instance group.The default value for master and worker groups is NON_PREEMPTIBLE. This default cannot be changed.The default value for secondary instances is PREEMPTIBLE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..metastore-config dataproc-metastore-service=stet</code></p>
|
||||
<ul>
|
||||
<li>Required. Resource name of an existing Dataproc Metastore service.Example: projects/[project_id]/locations/[dataproc_region]/services/[service-name]</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..secondary-worker-config.disk-config boot-disk-size-gb=41</code></p>
|
||||
<ul>
|
||||
<li>Optional. Size in GB of the boot disk (default is 500GB).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>boot-disk-type=clita</code><ul>
|
||||
<li>Optional. Type of the boot disk (default is "pd-standard"). Valid values: "pd-balanced" (Persistent Disk Balanced Solid State Drive), "pd-ssd" (Persistent Disk Solid State Drive), or "pd-standard" (Persistent Disk Hard Disk Drive). See Disk types (https://cloud.google.com/compute/docs/disks#disk-types).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>num-local-ssds=5</code></p>
|
||||
<ul>
|
||||
<li>Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. image-uri=dolores</code></p>
|
||||
<ul>
|
||||
<li>Optional. The Compute Engine image resource used for cluster instances.The URI can represent an image or image family.Image examples: https://www.googleapis.com/compute/beta/projects/[project_id]/global/images/[image-id] projects/[project_id]/global/images/[image-id] image-idImage family examples. Dataproc will use the most recent image from the family: https://www.googleapis.com/compute/beta/projects/[project_id]/global/images/family/[custom-image-family-name] projects/[project_id]/global/images/family/[custom-image-family-name]If the URI is unspecified, it will be inferred from SoftwareConfig.image_version or the system default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>instance-names=sit</code><ul>
|
||||
<li><code>instance-names=est</code><ul>
|
||||
<li>Output only. The list of instance names. Dataproc derives the names from cluster_name, num_instances, and the instance group.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
@@ -833,152 +806,227 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Output only. Specifies that this instance group contains preemptible instances.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>machine-type-uri=sanctus</code><ul>
|
||||
<li><code>machine-type-uri=et</code><ul>
|
||||
<li>Optional. The Compute Engine machine type used for cluster instances.A full URL, partial URI, or short name are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2 projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2 n1-standard-2Auto Zone Exception: If you are using the Dataproc Auto Zone Placement (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone#using_auto_zone_placement) feature, you must use the short name of the machine type resource, for example, n1-standard-2.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>managed-group-config instance-group-manager-name=kasd</code><ul>
|
||||
<li><code>managed-group-config instance-group-manager-name=labore</code><ul>
|
||||
<li>Output only. The name of the Instance Group Manager for this group.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>instance-template-name=eirmod</code></p>
|
||||
<p><code>instance-template-name=labore</code></p>
|
||||
<ul>
|
||||
<li>Output only. The name of the Instance Template used for the Managed Instance Group.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. min-cpu-platform=dolores</code></p>
|
||||
<p><code>.. min-cpu-platform=et</code></p>
|
||||
<ul>
|
||||
<li>Optional. Specifies the minimum cpu platform for the Instance Group. See Dataproc -> Minimum CPU Platform (https://cloud.google.com/dataproc/docs/concepts/compute/dataproc-min-cpu).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-instances=69</code><ul>
|
||||
<li><code>num-instances=19</code><ul>
|
||||
<li>Optional. The number of VM instances in the instance group. For HA cluster master_config groups, must be set to 3. For standard cluster master_config groups, must be set to 1.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>preemptibility=dolor</code></p>
|
||||
<p><code>preemptibility=ut</code></p>
|
||||
<ul>
|
||||
<li>Optional. Specifies the preemptibility of the instance group.The default value for master and worker groups is NON_PREEMPTIBLE. This default cannot be changed.The default value for secondary instances is PREEMPTIBLE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..security-config.identity-config user-service-account-mapping=key=vero</code></p>
|
||||
<p><code>..metastore-config dataproc-metastore-service=amet.</code></p>
|
||||
<ul>
|
||||
<li>Required. Resource name of an existing Dataproc Metastore service.Example: projects/[project_id]/locations/[dataproc_region]/services/[service-name]</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..secondary-worker-config.disk-config boot-disk-size-gb=89</code></p>
|
||||
<ul>
|
||||
<li>Optional. Size in GB of the boot disk (default is 500GB).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>boot-disk-type=est</code><ul>
|
||||
<li>Optional. Type of the boot disk (default is "pd-standard"). Valid values: "pd-balanced" (Persistent Disk Balanced Solid State Drive), "pd-ssd" (Persistent Disk Solid State Drive), or "pd-standard" (Persistent Disk Hard Disk Drive). See Disk types (https://cloud.google.com/compute/docs/disks#disk-types).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>local-ssd-interface=rebum.</code><ul>
|
||||
<li>Optional. Interface type of local SSDs (default is "scsi"). Valid values: "scsi" (Small Computer System Interface), "nvme" (Non-Volatile Memory Express). See local SSD performance (https://cloud.google.com/compute/docs/disks/local-ssd#performance).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>num-local-ssds=55</code></p>
|
||||
<ul>
|
||||
<li>Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. image-uri=erat</code></p>
|
||||
<ul>
|
||||
<li>Optional. The Compute Engine image resource used for cluster instances.The URI can represent an image or image family.Image examples: https://www.googleapis.com/compute/beta/projects/[project_id]/global/images/[image-id] projects/[project_id]/global/images/[image-id] image-idImage family examples. Dataproc will use the most recent image from the family: https://www.googleapis.com/compute/beta/projects/[project_id]/global/images/family/[custom-image-family-name] projects/[project_id]/global/images/family/[custom-image-family-name]If the URI is unspecified, it will be inferred from SoftwareConfig.image_version or the system default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>instance-names=dolor</code><ul>
|
||||
<li>Output only. The list of instance names. Dataproc derives the names from cluster_name, num_instances, and the instance group.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>is-preemptible=true</code><ul>
|
||||
<li>Output only. Specifies that this instance group contains preemptible instances.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>machine-type-uri=eirmod</code><ul>
|
||||
<li>Optional. The Compute Engine machine type used for cluster instances.A full URL, partial URI, or short name are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2 projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2 n1-standard-2Auto Zone Exception: If you are using the Dataproc Auto Zone Placement (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone#using_auto_zone_placement) feature, you must use the short name of the machine type resource, for example, n1-standard-2.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>managed-group-config instance-group-manager-name=amet.</code><ul>
|
||||
<li>Output only. The name of the Instance Group Manager for this group.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>instance-template-name=takimata</code></p>
|
||||
<ul>
|
||||
<li>Output only. The name of the Instance Template used for the Managed Instance Group.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. min-cpu-platform=amet.</code></p>
|
||||
<ul>
|
||||
<li>Optional. Specifies the minimum cpu platform for the Instance Group. See Dataproc -> Minimum CPU Platform (https://cloud.google.com/dataproc/docs/concepts/compute/dataproc-min-cpu).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-instances=79</code><ul>
|
||||
<li>Optional. The number of VM instances in the instance group. For HA cluster master_config groups, must be set to 3. For standard cluster master_config groups, must be set to 1.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>preemptibility=labore</code></p>
|
||||
<ul>
|
||||
<li>Optional. Specifies the preemptibility of the instance group.The default value for master and worker groups is NON_PREEMPTIBLE. This default cannot be changed.The default value for secondary instances is PREEMPTIBLE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..security-config.identity-config user-service-account-mapping=key=sed</code></p>
|
||||
<ul>
|
||||
<li>Required. Map of user to service account.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..kerberos-config cross-realm-trust-admin-server=ea</code></p>
|
||||
<p><code>..kerberos-config cross-realm-trust-admin-server=sit</code></p>
|
||||
<ul>
|
||||
<li>Optional. The admin server (IP or hostname) for the remote trusted realm in a cross realm trust relationship.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>cross-realm-trust-kdc=magna</code><ul>
|
||||
<li><code>cross-realm-trust-kdc=sit</code><ul>
|
||||
<li>Optional. The KDC (IP or hostname) for the remote trusted realm in a cross realm trust relationship.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>cross-realm-trust-realm=rebum.</code><ul>
|
||||
<li><code>cross-realm-trust-realm=invidunt</code><ul>
|
||||
<li>Optional. The remote realm the Dataproc on-cluster KDC will trust, should the user enable cross realm trust.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>cross-realm-trust-shared-password-uri=amet</code><ul>
|
||||
<li><code>cross-realm-trust-shared-password-uri=elitr</code><ul>
|
||||
<li>Optional. The Cloud Storage URI of a KMS encrypted file containing the shared password between the on-cluster Kerberos realm and the remote trusted realm, in a cross realm trust relationship.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>enable-kerberos=true</code><ul>
|
||||
<li><code>enable-kerberos=false</code><ul>
|
||||
<li>Optional. Flag to indicate whether to Kerberize the cluster (default: false). Set this field to true to enable Kerberos on a cluster.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kdc-db-key-uri=sadipscing</code><ul>
|
||||
<li><code>kdc-db-key-uri=amet.</code><ul>
|
||||
<li>Optional. The Cloud Storage URI of a KMS encrypted file containing the master key of the KDC database.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>key-password-uri=dolore</code><ul>
|
||||
<li><code>key-password-uri=aliquyam</code><ul>
|
||||
<li>Optional. The Cloud Storage URI of a KMS encrypted file containing the password to the user provided key. For the self-signed certificate, this password is generated by Dataproc.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>keystore-password-uri=amet</code><ul>
|
||||
<li><code>keystore-password-uri=et</code><ul>
|
||||
<li>Optional. The Cloud Storage URI of a KMS encrypted file containing the password to the user provided keystore. For the self-signed certificate, this password is generated by Dataproc.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>keystore-uri=invidunt</code><ul>
|
||||
<li><code>keystore-uri=gubergren</code><ul>
|
||||
<li>Optional. The Cloud Storage URI of the keystore file used for SSL encryption. If not provided, Dataproc will provide a self-signed certificate.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>kms-key-uri=invidunt</code><ul>
|
||||
<li><code>kms-key-uri=sed</code><ul>
|
||||
<li>Optional. The uri of the KMS key used to encrypt various sensitive files.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>realm=dolores</code><ul>
|
||||
<li><code>realm=no</code><ul>
|
||||
<li>Optional. The name of the on-cluster Kerberos realm. If not specified, the uppercased domain of hostnames will be the realm.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>root-principal-password-uri=diam</code><ul>
|
||||
<li><code>root-principal-password-uri=sit</code><ul>
|
||||
<li>Optional. The Cloud Storage URI of a KMS encrypted file containing the root principal password.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>tgt-lifetime-hours=43</code><ul>
|
||||
<li><code>tgt-lifetime-hours=94</code><ul>
|
||||
<li>Optional. The lifetime of the ticket granting ticket, in hours. If not specified, or user specifies 0, then default value 10 will be used.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>truststore-password-uri=sed</code><ul>
|
||||
<li><code>truststore-password-uri=elitr</code><ul>
|
||||
<li>Optional. The Cloud Storage URI of a KMS encrypted file containing the password to the user provided truststore. For the self-signed certificate, this password is generated by Dataproc.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>truststore-uri=eos</code></p>
|
||||
<p><code>truststore-uri=et</code></p>
|
||||
<ul>
|
||||
<li>Optional. The Cloud Storage URI of the truststore file used for SSL encryption. If not provided, Dataproc will provide a self-signed certificate.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>...software-config image-version=sit</code></p>
|
||||
<p><code>...software-config image-version=consetetur</code></p>
|
||||
<ul>
|
||||
<li>Optional. The version of software inside the cluster. It must be one of the supported Dataproc Versions (https://cloud.google.com/dataproc/docs/concepts/versioning/dataproc-versions#supported_dataproc_versions), such as "1.2" (including a subminor version, such as "1.2.29"), or the "preview" version (https://cloud.google.com/dataproc/docs/concepts/versioning/dataproc-versions#other_versions). If unspecified, it defaults to the latest Debian version.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>optional-components=et</code><ul>
|
||||
<li><code>optional-components=at</code><ul>
|
||||
<li>Optional. The set of components to activate on the cluster.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>properties=key=ea</code></p>
|
||||
<p><code>properties=key=et</code></p>
|
||||
<ul>
|
||||
<li>Optional. The properties to set on daemon config files.Property keys are specified in prefix:property format, for example core:hadoop.tmp.dir. The following are supported prefixes and their mappings: capacity-scheduler: capacity-scheduler.xml core: core-site.xml distcp: distcp-default.xml hdfs: hdfs-site.xml hive: hive-site.xml mapred: mapred-site.xml pig: pig.properties spark: spark-defaults.conf yarn: yarn-site.xmlFor more information, see Cluster properties (https://cloud.google.com/dataproc/docs/concepts/cluster-properties).</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. temp-bucket=dolor</code></p>
|
||||
<p><code>.. temp-bucket=accusam</code></p>
|
||||
<ul>
|
||||
<li>Optional. A Cloud Storage bucket used to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. If you do not specify a temp bucket, Dataproc will determine a Cloud Storage location (US, ASIA, or EU) for your cluster's temp bucket according to the Compute Engine zone where your cluster is deployed, and then create and manage this project-level, per-location bucket. The default bucket has a TTL of 90 days, but you can use any TTL (or none) if you specify a bucket. This field requires a Cloud Storage bucket name, not a URI to a Cloud Storage bucket.</li>
|
||||
<li>Optional. A Cloud Storage bucket used to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. If you do not specify a temp bucket, Dataproc will determine a Cloud Storage location (US, ASIA, or EU) for your cluster's temp bucket according to the Compute Engine zone where your cluster is deployed, and then create and manage this project-level, per-location bucket. The default bucket has a TTL of 90 days, but you can use any TTL (or none) if you specify a bucket (see Dataproc staging and temp buckets (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/staging-bucket)). This field requires a Cloud Storage bucket name, not a gs://... URI to a Cloud Storage bucket.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>worker-config.disk-config boot-disk-size-gb=56</code><ul>
|
||||
<li><code>worker-config.disk-config boot-disk-size-gb=3</code><ul>
|
||||
<li>Optional. Size in GB of the boot disk (default is 500GB).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>boot-disk-type=diam</code><ul>
|
||||
<li><code>boot-disk-type=voluptua.</code><ul>
|
||||
<li>Optional. Type of the boot disk (default is "pd-standard"). Valid values: "pd-balanced" (Persistent Disk Balanced Solid State Drive), "pd-ssd" (Persistent Disk Solid State Drive), or "pd-standard" (Persistent Disk Hard Disk Drive). See Disk types (https://cloud.google.com/compute/docs/disks#disk-types).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>local-ssd-interface=kasd</code><ul>
|
||||
<li>Optional. Interface type of local SSDs (default is "scsi"). Valid values: "scsi" (Small Computer System Interface), "nvme" (Non-Volatile Memory Express). See local SSD performance (https://cloud.google.com/compute/docs/disks/local-ssd#performance).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>num-local-ssds=74</code></p>
|
||||
<p><code>num-local-ssds=40</code></p>
|
||||
<ul>
|
||||
<li>Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. image-uri=at</code></p>
|
||||
<p><code>.. image-uri=amet.</code></p>
|
||||
<ul>
|
||||
<li>Optional. The Compute Engine image resource used for cluster instances.The URI can represent an image or image family.Image examples: https://www.googleapis.com/compute/beta/projects/[project_id]/global/images/[image-id] projects/[project_id]/global/images/[image-id] image-idImage family examples. Dataproc will use the most recent image from the family: https://www.googleapis.com/compute/beta/projects/[project_id]/global/images/family/[custom-image-family-name] projects/[project_id]/global/images/family/[custom-image-family-name]If the URI is unspecified, it will be inferred from SoftwareConfig.image_version or the system default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>instance-names=kasd</code><ul>
|
||||
<li><code>instance-names=aliquyam</code><ul>
|
||||
<li>Output only. The list of instance names. Dataproc derives the names from cluster_name, num_instances, and the instance group.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
@@ -987,11 +1035,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Output only. Specifies that this instance group contains preemptible instances.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>machine-type-uri=est</code><ul>
|
||||
<li><code>machine-type-uri=duo</code><ul>
|
||||
<li>Optional. The Compute Engine machine type used for cluster instances.A full URL, partial URI, or short name are valid. Examples: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2 projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2 n1-standard-2Auto Zone Exception: If you are using the Dataproc Auto Zone Placement (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone#using_auto_zone_placement) feature, you must use the short name of the machine type resource, for example, n1-standard-2.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>managed-group-config instance-group-manager-name=gubergren</code><ul>
|
||||
<li><code>managed-group-config instance-group-manager-name=kasd</code><ul>
|
||||
<li>Output only. The name of the Instance Group Manager for this group.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -1002,47 +1050,47 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. min-cpu-platform=dolore</code></p>
|
||||
<p><code>.. min-cpu-platform=no</code></p>
|
||||
<ul>
|
||||
<li>Optional. Specifies the minimum cpu platform for the Instance Group. See Dataproc -> Minimum CPU Platform (https://cloud.google.com/dataproc/docs/concepts/compute/dataproc-min-cpu).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>num-instances=62</code><ul>
|
||||
<li><code>num-instances=38</code><ul>
|
||||
<li>Optional. The number of VM instances in the instance group. For HA cluster master_config groups, must be set to 3. For standard cluster master_config groups, must be set to 1.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>preemptibility=stet</code></p>
|
||||
<p><code>preemptibility=sanctus</code></p>
|
||||
<ul>
|
||||
<li>Optional. Specifies the preemptibility of the instance group.The default value for master and worker groups is NON_PREEMPTIBLE. This default cannot be changed.The default value for secondary instances is PREEMPTIBLE.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>... labels=key=accusam</code></p>
|
||||
<p><code>... labels=key=gubergren</code></p>
|
||||
<ul>
|
||||
<li>Optional. The labels to associate with this cluster. Label keys must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). Label values may be empty, but, if present, must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). No more than 32 labels can be associated with a cluster.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>metrics hdfs-metrics=key=et</code><ul>
|
||||
<li><code>metrics hdfs-metrics=key=accusam</code><ul>
|
||||
<li>The HDFS metrics.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>yarn-metrics=key=dolor</code></p>
|
||||
<p><code>yarn-metrics=key=lorem</code></p>
|
||||
<ul>
|
||||
<li>The YARN metrics.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. project-id=diam</code></p>
|
||||
<p><code>.. project-id=dolor</code></p>
|
||||
<ul>
|
||||
<li>Required. The Google Cloud Platform project ID that the cluster belongs to.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>status detail=elitr</code><ul>
|
||||
<li><code>status detail=sanctus</code><ul>
|
||||
<li>Optional. Output only. Details of cluster's state.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -1050,11 +1098,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Output only. The cluster's state.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state-start-time=vero</code><ul>
|
||||
<li><code>state-start-time=diam</code><ul>
|
||||
<li>Output only. Time when this state was entered (see JSON representation of Timestamp (https://developers.google.com/protocol-buffers/docs/proto3#json)).</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>substate=et</code><ul>
|
||||
<li><code>substate=amet</code><ul>
|
||||
<li>Output only. Additional state information that includes status reported by the agent.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -1092,7 +1140,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
<li>
|
||||
<p><strong>-p request-id=string</strong></p>
|
||||
<ul>
|
||||
<li>Optional. A unique id used to identify the request. If the server receives two UpdateClusterRequest (https://cloud.google.com/dataproc/docs/reference/rpc/google.cloud.dataproc.v1#google.cloud.dataproc.v1.UpdateClusterRequest)s with the same id, then the second request will be ignored and the first google.longrunning.Operation created and stored in the backend is returned.It is recommended to always set this value to a UUID (https://en.wikipedia.org/wiki/Universally_unique_identifier).The id must contain only letters (a-z, A-Z), numbers (0-9), underscores (_), and hyphens (-). The maximum length is 40 characters.</li>
|
||||
<li>Optional. A unique ID used to identify the request. If the server receives two UpdateClusterRequest (https://cloud.google.com/dataproc/docs/reference/rpc/google.cloud.dataproc.v1#google.cloud.dataproc.v1.UpdateClusterRequest)s with the same id, then the second request will be ignored and the first google.longrunning.Operation created and stored in the backend is returned.It is recommended to always set this value to a UUID (https://en.wikipedia.org/wiki/Universally_unique_identifier).The ID must contain only letters (a-z, A-Z), numbers (0-9), underscores (_), and hyphens (-). The maximum length is 40 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
@@ -1179,7 +1227,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
|
||||
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
|
||||
|
||||
<a href="../projects_regions-clusters-set-iam-policy" class="btn btn-neutral float-right" title="Regions Clusters Set Iam Policy"/>Next <span class="icon icon-circle-arrow-right"></span></a>
|
||||
<a href="../projects_regions-clusters-repair" class="btn btn-neutral float-right" title="Regions Clusters Repair"/>Next <span class="icon icon-circle-arrow-right"></span></a>
|
||||
|
||||
|
||||
<a href="../projects_regions-clusters-list" class="btn btn-neutral" title="Regions Clusters List"><span class="icon icon-circle-arrow-left"></span> Previous</a>
|
||||
@@ -1211,7 +1259,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
<a class="icon icon-github" style="float: left; color: #fcfcfc"> GitHub</a>
|
||||
|
||||
<span><a href="../projects_regions-clusters-list" style="color: #fcfcfc;">« Previous</a></span>
|
||||
<span style="margin-left: 15px"><a href="../projects_regions-clusters-set-iam-policy" style="color: #fcfcfc">Next »</a></span>
|
||||
<span style="margin-left: 15px"><a href="../projects_regions-clusters-repair" style="color: #fcfcfc">Next »</a></span>
|
||||
</span>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
Reference in New Issue
Block a user