-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
loading LS might (rarely) fail due JRuby auto-load bug #12077
Labels
Comments
2 tasks
This was referenced Aug 23, 2021
Should be fixed by #13933 |
I got the same issue, running multiple pipelines in docker
|
the JRuby 9.3 upgrade was shipped at #14114 (we expect this issue to be resolved in Logstash >= 8.3.0) |
Closing this issue as the related work is now complete. This will be available in 8.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JRuby, being Ruby, uses RubyGems - a
require 'rubygems'
happens by default as the runtime starts.Some of the constants (such as
Gem::Specification
) are setup to auto-load on demand while also being explicitly required.This is problematic and known issue for JRuby 9K, it can be triggered when multiple threads try to do smt with an auto-loaded constant which has been explicitly required (sample reproducer at jruby/jruby#6293).
LS does use
Gem::Specification
as pipelines are being initialized, sample logged failure from LS 7.6.0 :HINT: The issue is rare to run into and users are advised to attempt to (re-)start.
A work-around is expected to be available with the release of RGs 3.1.5 (and 3.2.0), where auto-loaded parts are no longer being explicitly required. A proper fix is expected to be available in JRuby 9.3.
The text was updated successfully, but these errors were encountered: