4 ms·
Azure's ILBs are still just bizarre to me. It's the first load balancer I've ever worked with where sometimes a member of the pool can't reach the load balancer
by shanemhansen 8y ago
Azure's ILBs are still just bizarre to me. It's the first load balancer I've ever worked with where sometimes a member of the pool can't reach the load balancer. At the packet level given their implementation, this makes sense but tell me how many times you've ever had to write a stats endpoint where the stats nodes had to do workarounds to send their own stats?
Source: https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-overview#limitations https://docs.microsoft.com/en-us/azure/load-balancer/load-ba...
- outworlder 8y agoDo you have any information on their implementation? I only noticed that something was amiss once I connected a load balancer and my instances suddenly lost internet access. And also due to the limitation on how many load balancers you can have. It seems that once you add a load balancer, all traffic gets funneled through it, doesn't matter if it was addressed to it or not. Which is unlike any other load balancer I have ever seen. Coming from other clouds, this was a shock. The only thing comparable is AWS's NLB. Because that load balancer is so transparent, clients appear to be connecting directly, with the original source ip. Which caused issues when I wanted to deploy my own Elasticsearch and use an internal NLB for master discovery (whenever a request got routed to the same machine packets got discarded by the kernel). But you can just switch to another load balancer then.
- maglite77 8y agoDisclosure: Engineer at Microsoft There is an excellent Network Academy video on YouTube [1] that covers some of the internal implementations of the layer-4 load balancers (in the context of HA for NVA's). [1]: https://youtu.be/oYJBrWcOXfY https://youtu.be/oYJBrWcOXfY