I have already talked about the differences between the ILB and an ELB, but I have heard requests for specific reasons why the ILB should be used. How about I give you 12.
Cloud Architecture and Observability
Tag: Load balancer
I received a question recently on how to test if the Integrated Load Balancer (ILB) master goes down that another node actually takes over the VIP (i.e. failover). While there is technically no supported way to do this today, read on to learn how I would test this from the CLI.
Now that you know what the integrated load balancer feature is in Log Insight 2.5, you probably are interested in how you can switch from your already configured external load balancer (ELB) to the new integrated load balancer (ILB) and if you should switch. I will cover these topics in this post.
Log Insight 2.0 featured a scale-out option which relied on an external load balancer in order to support ingestion high availability. In Log Insight 2.5 an integrated load balancer is available. I would like to discuss the features of the integrated load balancer and also offer a comparison between using an external load balancer versus the integrated load balancer.
In my last post, I talked about two routing modes used on load balancers: NAT and transparent. As you may recall, I recommended against using transparent mode unless it is a common practice to use a load balancer as the default gateway in your environment. In this blog post, I would like to provide another workaround that would enable transparent mode without having to point the default gateway of your Log Insight nodes to the load balancer!
In my posts about load balancer configuration for Log Insight, I have talked about configuring Network Address Translation (NAT). I would like to dive a little deeper on the differences between NAT mode and another mode available on load balancers called transparency.
In Log Insight 2.0 a scale-out feature was introduced. The best practice when using scale-out is to configure an external load balancer in front of the cluster and send all ingestion traffic (i.e. syslog and ingestion API) to the load balancer instead of directly to a node. The reason for this best practice is to assist with balancing data across nodes and also to provide ingestion high availability. In this post, I would like to discuss why data may not be balanced across a Log Insight cluster whether a load balancer is used or not.
