By info186391
How do you handle the situation where you want to switch your load balancer node? Once the old one is destroyed you lose the IP address, DNS propagation of the new IP address can take several hours (or days even), so there will be an interruption in service for some users.
Am I missing something?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
You can (and probably should, for the reasons you cited) create the replacement droplet first; and get it up and running b/f destroying any of your current load-balancer nodes.
Yes, but it will have a different IP address, so when you switch over you’re relying on DNS propagation. Having 2 load balancers running at the same time for 2 days before and after the DNS change is made would work I suppose, seems a bit haphazard though. <br> <br>It would be much better if DO could provide some kind of dynamic external to internal IP mapping system, then a switchover could be almost instant.
What kind of load-balancing setup do you have? <br> <br>Couldn’t you deploy the new node; but b/f destroying the other node, you remove the DNS record for the node that you’re retiring. Wait 72 hours, and then destroy the node?
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.