Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calls to oracle should respond to 502/504 errors with longer timeouts #41

Open
seasidesparrow opened this issue Jan 13, 2025 · 0 comments
Assignees

Comments

@seasidesparrow
Copy link
Member

Currently, docmatch pipeline will respond to a 50x error returned by oracle service by waiting ten seconds and trying again, up to a limit ten retries. The service and/or the Solr searchers can get into states where they generate multiple 50x errors, leading to multiple attempts in a (relatively) short period of time. These states can last from minutes to hours, so giving an oracle call what amounts to a 100-second window to resolve is probably too short.

We should increase the timeouts as the number of timeouts increases, e.g. 10 seconds, 20 seconds, 30 seconds... or 10 seconds, 100 seconds, 1000 seconds. A linear scaling (sum(n*10)n=1,10) would lead to a 550-second window

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant