This topic describes how to redeploy an Elastic Compute Service (ECS) instance of big data instance families (excluding d3c) or instance families equipped with local SSDs (excluding i4p) in the ECS console. After the instance is redeployed, the instance is migrated to a different host.
- Operations described in this topic are applicable only to scenarios where system events occur on instances equipped with local disks.
- Before you redeploy an instance equipped with local disks, make sure that the following operations are complete:
- Connect to an ECS instance.
For more information about connection methods, see Connection methods .
- Optional: Isolate the read/write operations on the local disks at the application layer.
- If the instance runs a Linux operating system, add the nofail parameter to the /etc/fstab file for all data disks.
In this example, the nofail parameter is added for the /dev/vdd data disk.
/dev/vdd /mnt/vdd ext4 defaults,barrier=0,nofail 0 0
Parameter Description /dev/vdd The device name of the local disk, which is the Device value returned by the DescribeInstanceHistoryEvents operation. /mnt/vdd The mount point of the local disk, which can be queried by using the
mount | grep "/dev/vdd"command.
ext4 The file system type of the local disk, which can be queried by using the
barrier=0 The mount option used to disable barriers in the file system. nofail Indicates that the booting sequence of the ECS instance is not interrupted even if the local disk specified in the file system does not exist.
- Connect to an ECS instance.
System events that require local disks to be redeployed include Instance Redeployment Due to System Maintenance (
SystemMaintenance.Redeploy) and Instance Redeployment Due to System Error (
SystemFailure.Redeploy). These system events are applicable only to big data instance families (excluding d3c) and instance families equipped with local SSDs (excluding i4p). For more information, see O&M scenarios and system events for instances equipped with local disks.
- Log on to the ECS console.
- In the left-side navigation pane, click Events.
- In the left-side navigation pane of the Events page, click Local Disk-based Instance Events.
- On the Local Disk Damaged Events tab, find the instance whose local disks need to be redeployed and click Redeploy in the Actions column.
- In the Redeploy Instance dialog box, confirm the impact of redeployment, select I am aware of the risk of data loss., and then click OK.
What to do next
- If the instance has cloud data disks attached and the cloud data disks are not configured to automatically mount on instance startup, you must connect to the instance after it is redeployed and run the following command to mount the cloud data disks:
mount <Data disk partition> <Mount point>
- If the instance has local data disks attached, you must partition and format the local data disks. For more information, see Initialize a data disk whose size does not exceed 2 TiB on a Linux instance.