Hello
I’m using Gatling feature “Load testing several servers with client based load balancing” at https://gatling.io/docs/2.3/http/http_protocol/ to test an application against a cluster of servers. The application has several requests for one user, the first request got a token from one server node, and the second request uses the token from the first request as part of the request. I’m seeing the second request failed with a 400 and suspecting the two requests were sent to different server nodes and caused the failure. Is there a way to enforce the requests for the same user go to the same server node for this client based load balancing feature? Something like sticky in Nginx load balancer.
Thanks!
It’s wonderful! Thanks! Stephane. I need to make our Gatling libs to be 3.0.0 compatible, so not fully succeed yet.
One feedback, on 2.3.1, there is a data folder under user-files, but the data folder is not there in 3.0.0-RC1, it would be better to be there for compatibility reason.
One feedback, on 2.3.1, there is a data folder under user-files, but the data folder is not there in 3.0.0-RC1, it would be better to be there for compatibility reason.
This change is fully intended and Gatling 3 is a new major version as we do introduce such breaking changes.
Stéphane Landelle
GatlingCorp CEO
slandelle@gatling.io