2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
For Route53 failover routing to work properly, it is absolutely critical that your health checks work properly.
There are three different types of Active-Passive failover that can be set-up as mentioned in this doc - https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-types.html
- active-passive failover with one primary and one secondary resource
- active-passive failover with multiple primary and secondary resources
- active-passive failover with weighted records
In your case, which one have you configured?
Note: Please accept my answer if you like it. Thanks
0
thanks Indranil. In my case it is 1. active-passive failover with one primary and one secondary resource
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a 3 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a 2 ans
Did you notice problems under heavy load? If under load, the health check URL takes time to respond, because the machine is heavily loaded, it could lead to a failover. You should run performance tests and use vertical scaling or even better horizontal scaling (put an ALB in front of your EC2 machines) in each region, to better scale.
Another change to look at is to use containers and use either ECS or EKS for container orchestration. That would involve significant re-architecture though but in the end may be worth the effort.
you are right Indranil:
Indranil, I will explore your scaling suggestions!