By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

RDS Read Replica, binlog_format

0

Switching the binlog_format from the default MIXED to ROW does not reflect on the read replica instance. Although the primary instance correctly adopts the new value, the read replica initially show as having incompatible parameters before eventually transitioning to an available state but binlog_format is still MIXED. In the RDS logs, an event is recorded: "Database instance marked as incompatible-parameters. The Database could not be started". It's worth noting that automated backup is enabled for the read replica instance already.

Have you experienced this?

Topics
Migration & ModernizationAnalyticsDatabase
Tags
Amazon Relational Database ServiceMySQL
Language
English
lightbulb
asked 3 months ago241 views
1 Answer
1

Ensure that both the primary instance and the read replica are using the correct parameter groups. If you have custom parameter groups, you need to make sure the binlog_format is set to ROW in both parameter groups.

profile picture
EXPERT
Mina Gobrial - OptimeCloud
answered 3 months ago
  • lightbulb
    3 months ago

    Both primary and replica instance are using the same parameter group, binlog_format is set to ROW in parameter group and primary instance correctly reflects it while read replica reflects MIXED. I believe it is due to incompatible-parameters error observed, hence it didn't get updated but unsure why it happened.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content