We have a HAProxy-cluster setup where we have configured our DNS to point at two HAProxy servers:
When we shutdown the HAProxy running at 184.108.40.206, gatling starts choking, instead of sending traffic to the HAProxy running at 220.127.116.11
If I’m correct, DNS resoultion in gatling is handled by org.asynchttpclient.channel.NameResolver.JdkNameResolver, but that will only return the first ip address from DNS.
Apparently, most browsers behave differently - for instance they might fallback to the second ip address when the first one is unavailable, or use alternating ip addresses between requests.
- Wouldn’t it make sense to create a few NameResolvers that match different browsers/clients in AHC?
- Wouldn’t it make sense to make the NameResolver pluggable/configurable in gatling to match browser behaviour?