All Products
Search

This Product

    Tair (Redis® OSS-Compatible):Restart an instance

    Document Center

    Tair (Redis® OSS-Compatible):Restart an instance

    Last Updated:Mar 28, 2026

    Restart a Tair (Redis OSS-compatible) instance when connections exceed the upper limit or access exceptions occur.

    Before you begin

    Review the following risks before restarting:

    • Data loss: Restart may cause data loss. The risk depends on your instance type. For details, see the FAQ below.

    • Transient connections: The instance experiences brief connection interruptions during restart. Make sure your applications can reconnect automatically before proceeding.

    Restart an instance from the console

    1. Log on to the console and go to the Instances page. In the top navigation bar, select the region where the instance resides.

    2. In the Actions column for the target instance, click restart.

    3. In the panel that appears, set the Restart Mode:

      • Restart Now: The instance restarts immediately.

      • Restart Within Maintenance Window: The instance restarts during the configured maintenance window. For more information, see Set a maintenance window.

    4. Read the risk notice, select the confirmation checkbox, and click OK.

    Complete secondary authentication (such as Multi-Factor Authentication (MFA)) as prompted. After you pass authentication, no re-authentication is required for 15 minutes.

    FAQ

    Why does the instance stay in the Restarting state after I restart it?

    After you restart a Redis Open-Source Edition or Tair (Enterprise Edition) instance, the instance state changes to Restarting immediately — this is expected.

    If you selected Restart Within Maintenance Window, the actual restart (master-replica switchover or shard failover) happens inside the maintenance window. The instance continues serving traffic normally until the maintenance window begins.

    How long does a restart take?

    A restart typically completes within 10 minutes.

    Does a restart cause data loss?

    It depends on the instance type:

    • High-availability master-replica instance: Data loss generally does not occur. However, if heavy read/write operations before the restart cause replication lag, any data not yet synced to the replica node may be lost.

    • Standalone instance: Data loss may occur. Exercise caution when you restart the instance. If your workload requires high data reliability, upgrade to a high-availability master-replica instance.