The problem is that when updating article translations
multiple requests to zendesk api are created in parallel
and at some point the zendesk service could respond
with error 503 or similar (too busy)
The solution given is to apply a retries mechanism in order
to call the failed request at some other point in time which
could lead to a successful response.
The mechanism is a backoff retry with jitter.
The number of retries is 5 per request.
How to test
Please setup a local environment and use it to generate article translations
with local server/db.
Reviewer checklist
Code:
[ ] Change is covered by unit-tests
[ ] Code is well documented, well styled and is following best practices
[ ] Performance issues have been taken under consideration
[ ] Errors and other edge-cases are handled properly
PR:
[ ] Problem and/or solution are well-explained
[ ] Commits have been squashed so that each one has a clear purpose
Problem and/or solution
The problem is that when updating article translations multiple requests to zendesk api are created in parallel and at some point the zendesk service could respond with error 503 or similar (too busy)
The solution given is to apply a retries mechanism in order to call the failed request at some other point in time which could lead to a successful response. The mechanism is a backoff retry with jitter. The number of retries is 5 per request.
How to test
Please setup a local environment and use it to generate article translations with local server/db.
Reviewer checklist
Code:
PR: