Closed vponomaryov closed 2 months ago
The problem with the previous behavior was that it kept retrying even on obvious user errors, like invalid query string in the script. And because the default retry count was high, it looked as if it froze.
I think in this case we need to add a parameter for controlling retries to select whether we want to retry only on timeout / overload errors (current behavior) or on all errors.
Using latest latte version it stops execution on the first failed query having retries be configured:
In the above example I brought down 1 DB node from 3 having CL=ALL. Having 10 configured retries, I expect it all to be applied (and be long enough to survive that node come back to UN time). Instead I got latte stress crash.
Looks like it is direct cause of the following change: https://github.com/pkolaczk/latte/commit/8cbbe2b510903155bb01f55525ec8c4a402bcac8