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

2 réponses
0
Réponse acceptée

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.

répondu il y a un an
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
MODÉRATEUR
philaws
répondu il y a un an
  • 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.

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions