Skip to content
This repository has been archived by the owner on Sep 16, 2023. It is now read-only.

feat: Additional fields for the ClusterConfig and InstanceGroupConfig messages. #253

Merged
merged 1 commit into from Jul 31, 2020
Merged

feat: Additional fields for the ClusterConfig and InstanceGroupConfig messages. #253

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
40 changes: 32 additions & 8 deletions ...ud-dataproc-v1/src/main/java/com/google/cloud/dataproc/v1/BasicYarnAutoscalingConfig.java
View file
Open in desktop
Expand Up @@ -209,11 +209,14 @@ public com.google.protobuf.DurationOrBuilder getGracefulDecommissionTimeoutOrBui
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to add workers. A scale-up factor of 1.0 will result in scaling
* up so that there is no pending memory remaining after the update (more
* aggressive scaling). A scale-up factor closer to 0 will result in a smaller
* magnitude of scaling up (less aggressive scaling).
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand All @@ -232,11 +235,14 @@ public double getScaleUpFactor() {
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to remove workers. A scale-down factor of 1 will result in
* scaling down so that there is no available memory remaining after the
* update (more aggressive scaling). A scale-down factor of 0 disables
* removing workers, which can be beneficial for autoscaling a single job.
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand Down Expand Up @@ -952,11 +958,14 @@ public com.google.protobuf.DurationOrBuilder getGracefulDecommissionTimeoutOrBui
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to add workers. A scale-up factor of 1.0 will result in scaling
* up so that there is no pending memory remaining after the update (more
* aggressive scaling). A scale-up factor closer to 0 will result in a smaller
* magnitude of scaling up (less aggressive scaling).
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand All @@ -972,11 +981,14 @@ public double getScaleUpFactor() {
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to add workers. A scale-up factor of 1.0 will result in scaling
* up so that there is no pending memory remaining after the update (more
* aggressive scaling). A scale-up factor closer to 0 will result in a smaller
* magnitude of scaling up (less aggressive scaling).
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand All @@ -995,11 +1007,14 @@ public Builder setScaleUpFactor(double value) {
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to add workers. A scale-up factor of 1.0 will result in scaling
* up so that there is no pending memory remaining after the update (more
* aggressive scaling). A scale-up factor closer to 0 will result in a smaller
* magnitude of scaling up (less aggressive scaling).
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand All @@ -1019,11 +1034,14 @@ public Builder clearScaleUpFactor() {
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to remove workers. A scale-down factor of 1 will result in
* scaling down so that there is no available memory remaining after the
* update (more aggressive scaling). A scale-down factor of 0 disables
* removing workers, which can be beneficial for autoscaling a single job.
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand All @@ -1039,11 +1057,14 @@ public double getScaleDownFactor() {
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to remove workers. A scale-down factor of 1 will result in
* scaling down so that there is no available memory remaining after the
* update (more aggressive scaling). A scale-down factor of 0 disables
* removing workers, which can be beneficial for autoscaling a single job.
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand All @@ -1062,11 +1083,14 @@ public Builder setScaleDownFactor(double value) {
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to remove workers. A scale-down factor of 1 will result in
* scaling down so that there is no available memory remaining after the
* update (more aggressive scaling). A scale-down factor of 0 disables
* removing workers, which can be beneficial for autoscaling a single job.
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand Down
10 changes: 8 additions & 2 deletions ...oc-v1/src/main/java/com/google/cloud/dataproc/v1/BasicYarnAutoscalingConfigOrBuilder.java
View file
Open in desktop
Expand Up @@ -80,11 +80,14 @@ public interface BasicYarnAutoscalingConfigOrBuilder
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to add workers. A scale-up factor of 1.0 will result in scaling
* up so that there is no pending memory remaining after the update (more
* aggressive scaling). A scale-up factor closer to 0 will result in a smaller
* magnitude of scaling up (less aggressive scaling).
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand All @@ -98,11 +101,14 @@ public interface BasicYarnAutoscalingConfigOrBuilder
*
*
* <pre>
* Required. Fraction of average pending memory in the last cooldown period
* Required. Fraction of average YARN pending memory in the last cooldown period
* for which to remove workers. A scale-down factor of 1 will result in
* scaling down so that there is no available memory remaining after the
* update (more aggressive scaling). A scale-down factor of 0 disables
* removing workers, which can be beneficial for autoscaling a single job.
* See [How autoscaling
* works](/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
* for more information.
* Bounds: [0.0, 1.0].
* </pre>
*
Expand Down