password of the new machine, or use the -i option to specify the private key file. If you see the Scaled cluster out successfully, the scale-out operation is successfully completed. 3. Check --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see the Scaled cluster in successfully, the scale-in op- eration is successfully completed. 3. Check Check the cluster status: The scale-in process takes some time. If the status of the node to be scaled in becomes Tombstone, that means the scale-in operation is successful. To check the scale-in status

Similar to steps in “Add the plugin to an existing cluster”. You need to specify the node that is scaled out (the ID shown by the tiup cluster display) with the -N parameter. Note that you need to upload

password of the new machine, or use the -i option to specify the private key file. If you see the Scaled cluster out successfully, the scale-out operation is successfully completed. 3. Check --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see the Scaled cluster in successfully, the scale-in op- eration is successfully completed. 3. Check Check the cluster status: The scale-in process takes some time. If the status of the node to be scaled in becomes Tombstone, that means the scale-in operation is successful. To check the scale-in status

password of the new machine, or use the -i option to specify the private key file. If you see the Scaled cluster out successfully, the scale-out operation is successfully completed. 3. Check --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see the Scaled cluster in successfully, the scale-in op- eration is successfully completed. 3. Check Check the cluster status: The scale-in process takes some time. If the status of the node to be scaled in becomes Tombstone, that means the scale-in operation is successful. To check the scale-in status

access to the target machine. [-p] is used to input the user password interactively. If you see Scaled cluster out successfully, the scale-out oper- ation succeeds. 3. Check the cluster --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see Scaled cluster in successfully, the scale-in opera- tion succeeds. 3. Check the cluster following command to check the scale-in status: tiup cluster display If the node to be scaled in becomes Tombstone, the scale-in operation succeeds. Access the monitoring platform at http://10

access to the target machine. [-p] is used to input the user password interactively. If you see Scaled cluster out successfully, the scale-out oper- ation succeeds. 3. Check the cluster --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see Scaled cluster in successfully, the scale-in opera- tion succeeds. 3. Check the cluster following command to check the scale-in status: tiup cluster display If the node to be scaled in becomes Tombstone, the scale-in operation succeeds. Access the monitoring platform at http://10

access to the target machine. [-p] is used to input the user password interactively. If you see Scaled cluster out successfully, the scale-out oper- ation succeeds. 3. Refresh the cluster --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see Scaled cluster in successfully, the scale-in opera- tion succeeds. 3. Refresh the cluster following command to check the scale-in status: tiup cluster display If the node to be scaled in becomes Tombstone, the scale-in operation succeeds. Access the monitoring platform at http://10

access to the target machine. [-p] is used to input the user password interactively. If you see Scaled cluster out successfully, the scale-out oper- ation succeeds. 3. Check the cluster --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see Scaled cluster in successfully, the scale-in opera- tion succeeds. 3. Check the cluster following command to check the scale-in status: tiup cluster display If the node to be scaled in becomes Tombstone, the scale-in operation succeeds. Access the monitoring platform at http://10

access to the target machine. [-p] is used to input the user password interactively. 872 If you see Scaled cluster out successfully, the scale-out oper- ation succeeds. 3. Refresh the cluster --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see Scaled cluster in successfully, the scale-in opera- tion succeeds. 3. Refresh the cluster following command to check the scale-in status: tiup cluster display If the node to be scaled in becomes Tombstone, the scale-in operation succeeds. Access the monitoring platform at http://10

access to the target machine. [-p] is used to input the user password interactively. If you see Scaled cluster out successfully, the scale-out oper- ation succeeds. 3. Refresh the cluster --node 10.0.1.5:20160 The --node parameter is the ID of the node to be taken offline. If you see Scaled cluster in successfully, the scale-in opera- tion succeeds. 3. Refresh the cluster following command to check the scale-in status: tiup cluster display If the node to be scaled in becomes Tombstone, the scale-in operation succeeds. Access the monitoring platform at http://10