Stopping Group Replication on a DB instance in an active-active cluster - Amazon Relational Database Service
Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

Stopping Group Replication on a DB instance in an active-active cluster

You can stop Group Replication on a DB instance in an active-active cluster. When you stop Group Replication, the DB instance is placed in super-read-only mode until replication is restarted or that DB instance is removed from the active-active cluster. For information about super-read-only mode, see the MySQL documentation.

To stop Group Replication temporarily for an active-active cluster
  1. Connect to a DB instance in the active-active cluster using a SQL client.

    For more information about connecting to an RDS for MySQL DB instance, see Connecting to your MySQL DB instance.

  2. In the SQL client, call the mysql.rds_group_replication_stop stored procedure:

    call mysql.rds_group_replication_stop();

To restart Group Replication so that the DB instance rejoins the active-active cluster, call the mysql.rds_group_replication_start stored procedure on the DB instance. For RDS for MySQL 9.7, first synchronize local GTIDs. For more information, see Synchronizing local GTIDs before a DB instance joins an active-active cluster (MySQL 9.7).

call mysql.rds_group_replication_start(0);