Enable the native replication feature

The native replication feature allows the privileged account to execute the following MySQL native replication statements:

• CHANGE MASTER TO: configures the replication between the primary database and the secondary database.

  For more information, see CHANGE MASTER TO.

• START SLAVE;: starts a replication process.

  For more information, see START SLAVE.

• STOP SLAVE;: stops a replication process.

  For more information, see STOP SLAVE.

• RESET SLAVE;: resets the status of the secondary database and restarts the replication process from the primary database.

  For more information, see RESET SLAVE.

The native replication feature allows the privileged account to execute SQL statements to modify specific parameters:

• Specify the read-only mode for the database server.

  SET GLOBAL read_only = ON/OFF;

  If you use the SET GLOBAL read_only = ON setting, the database server can process only read requests. If you use the SET GLOBAL read_only = OFF setting, the database server can process read and write requests.

• Specify whether to record the SQL statements that are executed in the current session to binary logs.

  SET SESSION sql_log_bin = ON/OFF;

  If you use the SET SESSION sql_log_bin = ON setting, the SQL statements that are executed in the current session are recorded to binary logs. If you use the SET SESSION sql_log_bin = OFF setting, the SQL statements that are executed in the current session are not recorded to binary logs.

• Specify the next global transaction identifier (GTID).

  SET SESSION GTID_NEXT = "your_gtid_value";

• Limits on privileged accounts

  Specific super permissions of the native replication feature are granted to the privileged account of the RDS instance. Only the privileged account can execute native replication statements, such as CHANGE MASTER and START SLAVE.

• Replication permission limits

  When you use the native replication feature to apply external binary logs, the native replication feature first checks the permissions. The binary logs that record operations not listed in the following section are not applied and the replication is interrupted.

  GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, 
  DROP, RELOAD, PROCESS, REFERENCES, INDEX,
  ALTER, SHOW DATABASES, CREATE TEMPORARY TABLES,
  LOCK TABLES, EXECUTE, REPLICATION SLAVE,
  REPLICATION CLIENT, CREATE VIEW, SHOW VIEW,
  CREATE ROUTINE, ALTER ROUTINE, CREATE USER, 
  EVENT, TRIGGER ON *.* TO XXX; 

• System database limits

  All operations on system databases are ignored. System databases include mysql, sys, information_schema, performance_schema, and __recyclebin__.

  Note

  Operations that indirectly modify databases, such as CREATE USER and GRANT, are not ignored. However, SQL statements must comply with the limits on replication permissions. Unauthorized operations, such as GRANT super on *.* to xxx;, interrupt the replication process.

• GTID limits

  In MySQL native replication, the GTID modes of the primary and secondary databases must be the same. You cannot disable the GTID mode for an RDS instance. If your RDS instance serves as a secondary database and you want to establish a replication relationship between the RDS instance and an external primary database, you must enable the GTID mode for the external primary database to prevent compatibility issues.

  Before you establish the replication relationship, you must execute the SHOW VARIABLES LIKE 'gtid_mode'; statement on the external primary database to check whether the GTID mode is enabled. If the GTID mode is disabled, run the SET GLOBAL gtid_mode=ON; command to enable the GTID mode for the external primary database.

• You cannot upgrade the major engine version of your RDS instance.

• You cannot upgrade the RDS edition of your RDS instance from RDS Basic Edition to RDS High-availability Edition or RDS Cluster Edition.

• You cannot switch your RDS instance to a different VPC.

• You cannot use the restoration feature for individual databases and tables.