Why Are Requests from the Same IP Address Routed to Different Backend Servers When the Load Balancing Algorithm Is Source IP Hash?
One possible cause is that the backend server receiving requests from the client has become unhealthy. The source IP hash algorithm uses the source IP address of each request as a hashing key to route traffic from a particular client to the same backend server, as long as it is available. This allows requests from different clients to be routed based on their source IP addresses and ensures that a given client is always directed to the same backend server.
However, if a backend server become unhealthy and then recovers, ELB will generate a new hash key based on the source IP address of the request and numbers the backend server. As a result, requests from the same IP address are routed to different backend servers.
Load Balancers FAQs
- What Is Quota?
- How Does ELB Distribute Traffic?
- How Can I Access a Load Balancer Across VPCs?
- How Can I Configure Load Balancing for Containerized Applications?
- Why Can't I Delete My Load Balancer?
- Do I Need to Configure EIP Bandwidth for My Load Balancers?
- Can I Bind Multiple EIPs to a Load Balancer?
- Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load Balancer?
- Why Are Requests from the Same IP Address Routed to Different Backend Servers When the Load Balancing Algorithm Is Source IP Hash?
- Can Backend Servers Access the Internet Using the EIP of the Load Balancer?
- Do Shared Load Balancers Have Specifications?
- Will Traffic Routing Be Interrupted If the Load Balancing Algorithm Is Changed?
- What Is the Difference Between the Bandwidth Included in Each Specification of a Dedicated Load Balancer and the Bandwidth of an EIP?
- How Do I Combine ELB and WAF?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore