You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/models/CreateScalingConfigurationRequest.java
+46Lines changed: 46 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,14 @@ public class CreateScalingConfigurationRequest extends Request {
* <p>The name of the image family. If you specify this parameter, the most recent custom images that are available in the specified image family are returned. You can use the images to create instances. If you specify ImageId, you cannot specify ImageFamily.</p>
Copy file name to clipboardExpand all lines: ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/models/CreateScalingGroupRequest.java
+20-7Lines changed: 20 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1247,7 +1247,20 @@ public Builder spotInstanceRemedy(Boolean spotInstanceRemedy) {
1247
1247
}
1248
1248
1249
1249
/**
1250
-
* StopInstanceTimeout.
1250
+
* <p>The period of time required by the ECS instance to enter the Stopped state. Unit: seconds. Valid values: 30 to 240.</p>
1251
+
* <blockquote>
1252
+
* </blockquote>
1253
+
* <ul>
1254
+
* <li><p>This parameter takes effect only if you set ScalingPolicy to release.</p>
1255
+
* </li>
1256
+
* <li><p>If you specify this parameter, the system will wait for the ECS instance to enter the Stopped state for the specified period of time before continuing with the scale-in operation, regardless of the status of the ECS instance.</p>
1257
+
* </li>
1258
+
* <li><p>If you do not specify this parameter, the system will wait for the ECS instance to stop before continuing with the scale-in operation. If the ECS instance is not successfully stopped, the scale-in process will be rolled back and considered failed.</p>
@@ -1742,7 +1755,7 @@ public static final class Builder {
1742
1755
/**
1743
1756
* <p>The action that Auto Scaling performs when the lifecycle hook times out. Valid values:</p>
1744
1757
* <ul>
1745
-
* <li>CONTINUE: Auto Scaling continues to respond to a scale-in or scale-out request.</li>
1758
+
* <li>CONTINUE: Auto Scaling continues to respond to the scaling request.</li>
1746
1759
* <li>ABANDON: Auto Scaling releases ECS instances that are created during scale-out events, or removes ECS instances from the scaling group during scale-in events.</li>
1747
1760
* </ul>
1748
1761
* <p>If multiple lifecycle hooks in the scaling group are triggered during scale-in events, and you set DefaultResult to ABANDON for one of the lifecycle hooks, Auto Scaling immediately performs the action after the lifecycle hook whose DefaultResult is set to ABANDON times out. In this case, other lifecycle hooks time out ahead of schedule. In other cases, Auto Scaling performs the action only after all lifecycle hooks time out. The action that Auto Scaling performs is determined by the value of DefaultResult that you specify for the lifecycle hook that most recently times out.</p>
@@ -1758,7 +1771,7 @@ public Builder defaultResult(String defaultResult) {
1758
1771
1759
1772
/**
1760
1773
* <p>The period of time before the lifecycle hook times out. When the lifecycle hook times out, Auto Scaling performs the action that is specified by DefaultResult. Valid values: 30 to 21600. Unit: seconds.</p>
1761
-
* <p>After you create a lifecycle hook, you can call the RecordLifecycleActionHeartbeat operation to extend the timeout period of the lifecycle hook. You can also call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of scheduled.</p>
1774
+
* <p>After you create a lifecycle hook, you can call the RecordLifecycleActionHeartbeat operation to extend the timeout period of the lifecycle hook. You can also call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule.</p>
1762
1775
* <p>Default value: 600.</p>
1763
1776
*
1764
1777
* <strong>example:</strong>
@@ -1799,15 +1812,15 @@ public Builder lifecycleTransition(String lifecycleTransition) {
1799
1812
}
1800
1813
1801
1814
/**
1802
-
* <p>The identifier of the notification recipient party when the lifecycle hook takes effect. You can specify a Message Service (MNS) topic or queue as the notification recipient party. Specify the value in the acs:ess:{region}:{account-id}:{resource-relative-id} format.</p>
1815
+
* <p>The Alibaba Cloud Resource Name (ARN) of the notification recipient party. You can specify a Simple Message Queue (SMQ, formerly MNS) topic or queue as the recipient party. The value is in the acs:ess:{region}:{account-id}:{resource-relative-id} format.</p>
1803
1816
* <ul>
1804
1817
* <li>region: the region ID of the scaling group</li>
1805
1818
* <li>account-id: the ID of your Alibaba Cloud account.</li>
@@ -1819,7 +1832,7 @@ public Builder notificationArn(String notificationArn) {
1819
1832
}
1820
1833
1821
1834
/**
1822
-
* <p>The fixed string that you want to include in a notification. When a lifecycle hook takes effect, Auto Scaling sends a notification. The fixed string can contain up to 4,096 characters in length. When Auto Scaling sends a notification to the recipient party, it includes predefined notification metadata into the notification. This helps in managing and labeling notifications of different categories. notificationmetadata takes effect only if you specify notificationarn.</p>
1835
+
* <p>The fixed string that you want to include in notifications. When a lifecycle hook takes effect, Auto Scaling sends a notification. The fixed string can contain up to 4,096 characters in length. When Auto Scaling sends a notification to the recipient party, it includes predefined notification metadata into the notification. This helps in managing and labeling notifications of different categories. NotificationMetadata takes effect only if you specify NotificationArn.</p>
* <p>The preemption policy that you want to apply to pay-as-you-go instances. The preemption policy specified by this parameter overwrites the preemption policy specified in the scaling configuration. Valid values:</p>
138
+
* <ul>
139
+
* <li>NoSpot: The instances are created as regular pay-as-you-go instances.</li>
140
+
* <li>SpotWithPriceLimit: The instances are created as preemptible instances that have a user-defined maximum hourly price.</li>
141
+
* <li>SpotAsPriceGo: The instances are created as preemptible instances for which the market price at the time of purchase is automatically used as the bidding price.</li>
* <p>The categories of the system disks. The categories of the system disks specified by this parameter overwrite the categories of the system disks specified in the scaling configuration. Valid values:</p>
0 commit comments