All Products
Search
Document Center

ApsaraDB for Redis:Query the synchronization latency between child instances

Last Updated:Mar 06, 2024

Global Distributed Cache for ApsaraDB for Redis features high performance and low latency. During the operation of the database system, you can query the synchronization status of child instances, the synchronization latency between child instances, and the amount of synchronized data at any time to gain real-time visibility into the status of synchronization channels.

Prerequisites

The Redis distributed instance that you want to manage contains at least two child instances. For information about how to add a child instance, see Add a child instance to a distributed instance.

Procedure

  1. Log on to the ApsaraDB for Redis console.

  2. In the left-side navigation pane, click Global Distributed Cache.

  3. Find the distributed instance that you want to manage and click the 加号 icon before the instance ID.

  4. Find the source instance for which you want to query the synchronization latency and click View Synchronization Status in the Actions column.

  5. In the dialog box that appears, select the time range to query, the data node of the source instance, and the destination instance.

    Note

    The maximum time range to query is the previous day.

    Figure 1. Synchronization status 同步状态

    Metric

    Description

    current_binlog_sync_delay_time

    The synchronization latency of binlogs. Unit: seconds. This synchronization latency is caused by the network latency between regions. Generally, a synchronization latency of less than 10 seconds is considered normal.

    Note

    If a high-availability switchover is triggered on a child instance, or if the instance undergoes maintenance operations such as a restart or configuration change, the synchronization latency for the instance may temporarily rise to around 60 minutes before returning to normal.

    ops

    The number of binlog entries that are synchronized from the specified data node of the source instance to the destination instance per second.

    status

    The synchronization status. Valid values:

    • 1: normal

    • 0: abnormal

FAQ

Why does the synchronization latency of binlogs suddenly increase or why is the synchronization status abnormal? How do I troubleshoot the issue?

If a high-availability switchover is triggered on a child instance, or if the instance undergoes maintenance operations such as a restart or configuration change, the synchronization latency for this instance increases. This increase is considered normal fluctuation and typically persists for a limited duration.

Related API operations

API operation

Description

DescribeGlobalDistributeCache

Queries the details of a distributed instance.