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

Investigate Strider connection errors on NodeNorm CI #276

Open
gaurav opened this issue Jul 5, 2024 · 0 comments
Open

Investigate Strider connection errors on NodeNorm CI #276

gaurav opened this issue Jul 5, 2024 · 0 comments

Comments

@gaurav
Copy link
Contributor

gaurav commented Jul 5, 2024

Aragorn/Strider is reporting a large number of connection timeouts when sending lots of requests to NodeNorm (see OTEL trace on CI at https://translator-otel.ci.transltr.io/trace/53f3945e7f9a5b34a8a26f1793b99cbb). Investigation revealed that there were no error messages in NodeNorm Web logs (as far as we could tell), and the presence of connection errors suggests that this is happening in Kubernetes before it gets to the web pod (but our logs may also be incomplete, see #275). We also found one Redis database (db1) running at 99.9% memory usage -- we'll upgrade that (helxplatform/translator-devops#935) and see if that makes any difference.

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