Restarting an Instance

Scenarios

You may need to restart an instance for routine maintenance.

Precautions

• Only instances in states Available, Abnormal, or Checking restoration can be restarted.
• After you restart an instance, all nodes in the instance are also restarted.
• Restarting an instance will interrupt services. Wait until off-peak hours and ensure that your application can re-connect.
• If you enable operation protection, two-factor authentication is required for sensitive operations to secure your account and cloud products. For details about how to enable operation protection, see Identity and Access Management User Guide.

Procedure

1. Log in to the GeminiDB console.
2. In the service list, choose Databases > GeminiDB Redis API.
3. On the Instances page, locate the instance you want to restart and in the Operation column choose Restart or More > Restart.

   Alternatively, locate the instance you want to restart and click its name. On the displayed Basic Information page, click Restart in the upper right corner of the page.

4. If you have enabled operation protection, click Start Verification in the Restart DB Instance dialog box. On the displayed page, click Send Code, enter the verification code, and click Verify. The page is closed automatically.
5. In the displayed dialog box, click Yes or Immediate.
   • Instance in classic deployment mode

     For GeminiDB Redis instances in classic deployment mode, you can restart several nodes at the same time or in sequence based on service requirements.

     Figure 1 Restarting an instance
     

   • Instance in cloud native deployment mode

     For GeminiDB Redis instances deployed in cloud native mode, click Yes or Immediate.

     Figure 2 Restarting an instance