-
Notifications
You must be signed in to change notification settings - Fork 0
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
Memory leak in Solr connections leading to Tomcat crash #14
Comments
Fix memory leaks for solr connection left open. Not sure why this wasn't an issue before. Maybe Tomcat would kill these threads after so long, and since we are getting pummeled with queries, the threads didn't have a chance to die. Either way, closing the solr client connections each time seems to fix it. Fixes #14
Fix memory leaks for solr connection left open. Not sure why this wasn't an issue before. Maybe Tomcat would kill these threads after so long, and since we are getting pummeled with queries, the threads didn't have a chance to die. Either way, closing the solr client connections each time seems to fix it. Cherry-picked from `hotfix/2.14.4` branch and `v2.14.4` release Fixes #14 Refs #15
This issue may have reared its head again, and may be related to the latest solrj upgrades: Additional leak possible in ds-view:
Here is a discussion on possible resolution upgrading Jetty to fix this leak. https://lists.apache.org/thread/n2rgq5l5jngbnpz8my9flk52zk7zg2xb |
Most likely tightly coupled with NASA-PDS/registry-legacy-solr#172 |
Nightly Tomcat restarts have been instantiated by SAs, and seems to avoiding this now. Not an ideal solution. But it works for now. Closing this. |
Still not fixed. It is pretty clear this is a leak in the Solr HTTP2Client. When trying to restart Tomcat:
|
Checked for duplicates
Yes - I've already checked
🐛 Describe the bug
When we got bombarded by openai crawling, Tomcat was spinning up too many open threads and crashing daily.
🕵️ Expected behavior
I expected we could take the traffic.
📜 To Reproduce
See SA logs and convo on Slack.
See these errors in catalina.out
And when you take ds-view offline, it is explicitly noting connection evictor issues related to
[ds-view]
, noting there is a memory leak spawning new threads and not closing them.🖥 Environment Info
Chrome
📚 Version of Software Used
v2.14.3
🩺 Test Data / Additional context
No response
🦄 Related requirements
No response
⚙️ Engineering Details
No response
The text was updated successfully, but these errors were encountered: