-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
CI failures due to file handle leaks #39585
Comments
Pinging @elastic/es-core-features |
The same error occurred in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+intake/638/
|
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+artifactory/649/consoleFull
Trace:
|
Pinging @elastic/es-distributed |
I had another failure which looks very similar on 7.x https://gradle-enterprise.elastic.co/s/fz4pznt6bautm
stacktrace
|
Got something very similar looking today in
https://gradle-enterprise.elastic.co/s/h4b5xjeymyqeo
|
I think this is a bug in Lucene where we do not properly close a FileChannel if we failed to create an NIOFSIndexInput. I will work on a fix for this on Lucene. |
I've opened apache/lucene-solr#1658 to propose a fix in Lucene. |
We are leaking a FileChannel in #39585 if we release a safe commit with CancellableThreads. Although it is a bug in Lucene where we do not close a FileChannel if we failed to create a NIOFSIndexInput, I think it's safer if we release a safe commit using the generic thread pool instead. Closes #39585 Relates #45409
We are leaking a FileChannel in #39585 if we release a safe commit with CancellableThreads. Although it is a bug in Lucene where we do not close a FileChannel if we failed to create a NIOFSIndexInput, I think it's safer if we release a safe commit using the generic thread pool instead. Closes #39585 Relates #45409
CI link: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/2317/console
This has failed a few times with similar errors recently, the earliest being Jan. 7 2019.
Does not reproduce locally, reproduce line:
Stack Trace:
Logs:
consoleText.txt
The text was updated successfully, but these errors were encountered: