RDS Read Replica, binlog_format

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?

主題

遷移與現代化分析資料庫

標籤

Amazon Relational Database Service MySQL

語言

English

lightbulb

已提問 3 個月前檢視次數 253 次

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.

專家

Mina Gobrial - OptimeCloud

已回答 3 個月前

lightbulb
3 個月前
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.

RDS Read Replica, binlog_format

相關內容