Reputation: 1245
While trying out a blue/green deployment for my Aurora Postgres database I noticed the following:
Prior to doing a switch over, I updated the database in the blue cluster and, as expected, the changes were replicated in the green cluster. However, when I updated data in the green cluster’s database, the changes weren’t replicated in the blue cluster. Is that the expected behavior?
It was unclear to me if the green cluster needed to have the rds.logical_replication turned ON or OFF. Since this site says it’s supposed to be ON and this site leads me to believe it should be OFF, I decided to try both scenarios. With rds.logical_replication ON, database updates in the blue cluster were not replicated in the green cluster; it only worked when rds.logical_replication was OFF. Is that the expected behavior?
I applied a custom parameter group with rds.logical_replication turned ON to the green cluster; this was specified before creation, not applied afterwards. Once the cluster was created, I ran the following query SELECT * FROM pg_catalog.pg_settings WHERE name = ‘rds.logical_replication’
and noticed that it was turned OFF. After doing a reboot rds.logical_replication was ON. Is having to do a reboot of the green cluster expected if we’re applying a custom parameter group?
Thanks for your help.
Upvotes: 0
Views: 12