2 個答案
- 最新
- 最多得票
- 最多評論
0
Hi,
Have a look at https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-get-started.html
Would configuration of traffic dial percentage be solution to your problem ?
Configure regional endpoint groups for your accelerator: You can select one or
more regional endpoint groups to add to your listener. The listener routes requests
to the endpoints that you've added to an endpoint group.
For a standard accelerator, Global Accelerator monitors the health of endpoints within
the group by using the health check settings that are defined for each of your endpoints.
For each endpoint group in a standard accelerator, you can configure a traffic dial percentage
to control the percentage of traffic that an endpoint group will accept. The percentage is
applied only to traffic that is already directed to the endpoint group, not all listener traffic. By
default, the traffic dial is set to 100% for all regional endpoint groups.
For a custom routing accelerators, traffic is deterministically routed to a specific destination in
a VPC subnet, based on the listener port that the traffic is received on.
Best,
Diidier
0
According to the documentation:
After each health check is completed, the listener closes the connection that was established for the health check.
This contradicts what you see in your environment.
I suggest you take traffic capture on your apache server using tools like tcpdump
to verify the actual behavior (e.g., that after the TCP handshake is established Global Accelerator sends or doesn't send FIN or RST to close the connection).
相關內容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
Thanks for your answer, but this isn't the problem.
The HEALTH CHECKS process create too many connections to all the servers behind the endpoint in global accelerator.
When the connections are created, this leave open in status "Reading Request" in my apaches servers. this is the problem