Help Center/ Distributed Cache Service/ User Guide/ Managing Lifecycle of an Instance/ Restarting a DCS Instance
Updated on 2024-10-17 GMT+08:00
View PDF
Share

Restarting a DCS Instance

To recover an instance in cases such as high memory fragmentation ratio or fault occurrence, try restarting the instance on the DCS console. DCS instances can be restarted in batches.

Notes and Constraints

  • The DCS instances must be in the Running or Faulty state.
  • For single-node instances or master/standby, cluster, and read/write splitting ones with AOF persistence disabled (parameter appendonly set to no), the instance data will be cleared after an instance restart. Exercise caution.
  • While a DCS instance is restarting, it cannot be read or written.
  • An attempt to restart a DCS instance while it is being backed up cancels the backup task, or may result in a failure.
  • Restarting a DCS instance will disconnect the original client. You are advised to configure automatic reconnection in your application.

Restarting a DCS Instance

  1. Log in to the DCS console.
  2. Click in the upper left corner of the management console and select the region where your instance is located.
  3. In the navigation pane, choose Cache Manager.
  4. Select the names of one or more desired DCS instances and click Restart above the list.

    To restart one instance, you can also locate the row containing the desired instance, and click Restart in the Operation column.

  5. In the displayed dialog box, click Yes. After DCS instances are restarted, their status changes to Running.

    The time required for restarting a DCS instance depends on the cache size of the instance. It make take 10s to 30 minutes.

    By default, only the instance process is restarted. If you select Force restart for a DCS Redis 3.0 or Memcached instance, its VM will be restarted. Force restart is not supported by DCS Redis 4.0 or later instances.