Modifying Specifications of Individual ECSs

Scenarios

If the ECS specifications do not meet service requirements, you can modify the specifications, including vCPUs and memory. Certain ECSs allow you to change their types when you modify their specifications.

Video

Notes

• The ECS needs to be stopped during the specification modification, so you are advised to perform this operation during off-peak hours.
• During the specification modification, do not perform any operation on the ECS, such as stopping or restarting the ECS. Otherwise, the modification will fail.
• When modifying the specifications of an ECS, sold-out vCPU and memory resources cannot be selected as new specifications.
• Downgrading ECS specifications (vCPUs or memory) will reduce performance.
• Certain ECS types do not support specification modification. For details about ECS types and functions, see ECS Types. For details about constraints on using different types of ECSs, see their notes.
• When the disk status is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.
• Before modifying the specifications of a Windows ECS, modify the SAN policy to prevent disks from going offline after the specifications are modified. For details, see Why Does a Disk Attached to a Windows ECS Go Offline?
• For yearly/monthly ECSs that use paid images, the instance specifications cannot be downgraded. This means you cannot change the specifications to lower-cost ones.

Billing

Modifying specifications will change how much you need to pay for the ECS. For details, see Pricing of a Changed Specification.

Preparations

After ECS specifications are modified, network interface flapping may occur. Before modifying the specifications, perform the following operations:

NIC flapping occurs because NIC retaining is enabled in the image from which the ECS is created.

For more information about network interface flapping, see What Should I Do If NIC Flapping Occurs After My ECS Specifications Are Modified?

• Linux

  Run the following commands on the ECS to delete the files with both persistent and net included in their names from the network rule directory:

  rm -fr /etc/udev/rules.d/*net*persistent*.rules

  rm -fr /etc/udev/rules.d/*persistent*net*.rules

• Windows

  Delete the following directories from the registry on the ECS:

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Unmanaged

  Figure 1 Registry
  

Step 1: Modify Specifications

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click . Under Compute, click Elastic Cloud Server.
4. Choose More > Modify Specifications in the Operation column.

   The Modify ECS Specifications page is displayed.

5. Select a new ECS type, vCPUs, and memory.

   You need to stop the ECS prior to the modification or select Authorize ECS auto-stop during the modification.

   Figure 2 Modifying specifications
   
6. Click Next.
7. Confirm the new specifications, read and agree to the agreement, and then click Submit Application.
8. Check whether the specifications have been modified.
   1. On the console, check whether Failures is displayed by referring to Viewing Failed Tasks.
      • If yes, go to step 8.b.
      • If no, the specifications have been modified.
   2. Click Failures. Then, in the Failures dialog box, click Operation Failures and check whether the task is contained in the list by Name/ID, Operated At, or Task.
      • If yes, the specifications failed to be modified. View the failure causes by referring to Follow-up Procedure.
      • If no, the specifications have been modified.

Step 2: Check Disk Attachment

After specifications are modified, disk attachment may fail. Therefore, check disk attachment after specification modification. If disks are properly attached, the specification modification is successful.

• Windows ECS

  For details, see Why Do the Disks of a Windows ECS Go Offline After I Modify the ECS Specifications?

• Linux ECS

  For details, see Why Does the Disk Attachment of a Linux ECS Fail After I Modify the ECS Specifications?

Follow-up Procedure

If the specifications fail to be modified, do as follows to view the failure cause:

1. Log in to the management console.
2. Under Management & Governance, click Cloud Trace Service.
3. In the navigation pane on the left, choose Trace List.
4. In the Trace Name column, locate resizeServer by resource ID.

   The resource ID is the ID of the ECS whose specifications failed to be modified.

5. Click the target trace name. In the slide-out Trace Overview panel, view the trace details and failure cause.

   If the fault cannot be rectified based on logs, contact customer service.