- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello,
Classic Load Balancer (CLB) hold two separate connections, front-end (client <> CLB) and Backend (CLB <> server). CLB will not terminate connections unless they reach the idle timeout (Ie, no data has been sent on the connection for X seconds). In other words, CLB will not forcefully terminate established and active connections to rebalance them because new backends has been added
When you add two more instances behind CLB, once they are registered and healthy, CLB will include these two new instances as part of its routing algorithm (round robin for TCP listener), for every new incoming connection, the request will land on any of the now 4 instances.
Note that cross-zone will also impact how your requests are distributed You can refer to https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/how-elastic-load-balancing-works.html for more detail.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa