Changing "primary" replication database

0

Im trying to follow this guide https://workmarket.tech/zero-downtime-maintenances-on-mysql-rds-ba13b51103c2 , for *active*-*active* replication.

But on command CHANGE *active* TO *active*_HOST=.... i get error: ERROR 1227 (42000): Access denied; you need (at least one of) the SUPER or REPLICATION_*secondary*_ADMIN privilege(s) for this operation

As i understood AWS forbids this kind of access via command line access. So, how do i then do this change? i assume via parameters group... but how?

*active* = some non inclusive word

*secondary* = some other non inclusive word

gefragt vor einem Jahr234 Aufrufe
2 Antworten
0
Akzeptierte Antwort

So, the "active-active" replication worked, there is just a some things that needs to be configured. As far as i understood those values in parameter groups of RDS DB must be configured:

auto_increment_increment
auto_increment_offset
log_bin_trust_function_creators

Then you also need to set the retention period

aws rds modify-db-instance --backup-retention-period 1 --db-instance-identifier <dbname> --apply-immediately

And then, just following any common guide of setup-ing the "active-active" replication should work.

beantwortet vor einem Jahr
0

There is a better option. RDS now support managed blue green deployment to make maintenance operations easier: https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-rds-blue-green-deployments-safer-simpler-faster-updates/

AWS
MODERATOR
philaws
beantwortet vor einem Jahr
  • It might be better solution in some cases, but in our case, we need to remove downtime fully, and this "blue/green deployment" solution does have downtime.

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen