uncleflo
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 1 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical network control beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community computer profile feature power browser music platform mobile work user process database share manage hardware professional buy industry internet dance advice installation developer 3d search access customer material travel camera test standard review documentation css money engineering develop webdesign engine device photography digital api speed source management program phone discussion question event client story simple water marketing yacht app content setup package fast idea interface account communication cheap compare script study market live easy google resource operation startup monitor training
Tag selected: unscheduled.
Looking up unscheduled tag. Showing 1 results. Clear
AWS - How to redirect database traffic to a new master on RDS after promoting a read replica? - Server Fault
Saved by uncleflo on June 23rd, 2019.
A lot of RDS's documentation about read replicas contains a magical step along the lines of "direct database traffic to the new master." For instance, their instructions on implementing failure recovery say: This talk about directing traffic glosses over what is actually a complicated step, though. If I were using EC2 instances to host my database, I could give them elastic IPs, use the public DNS address of the instance to address it (which resolves to its private IP from inside AWS), and then instantly swap my entire stack to the read replica by reassigning the elastic IP (and thus simultaneously reassigning the public DNS). I used this method happily back in the days when RDS was considered straightforwardly inferior to rolling your own database instance on EC2 by many DBAs. RDS instances still cannot have elastic IPs, though, so I cannot use this particular trick to magically redirect all my database traffic to a new instance when using RDS.
downtime unscheduled overflow fault deploy database answer server documentation automatic failover address reassign method rds inferior complicated disaster recovery instance host aurora instruction replication switch administration cloud aws howto discussion question
No further bookmarks found.