-
Notifications
You must be signed in to change notification settings - Fork 152
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
Possible deadlock on startup #635
Comments
Nice observation thank you! Since you're interested in contributing a fix I guess you're already working on it? |
I proposed something #637 |
@Dohbedoh. I've just found an interesting issue here. The constructor of |
…uice usage to avoid duplicate instantiation of DefaultPrometheusMetrics class.
…uice usage to avoid duplicate instantiation of DefaultPrometheusMetrics class. (#644)
@Waschndolos Should we maybe re-open this ? I still saw evidence of that problem in some instances running with latest versions of the plugin. The possibility that Collector kick during the initialization of a components is problematic because those collector eventually use extensions. |
@Dohbedoh I'm not sure how to solve it but to track it I'll reopen it. |
Proposed #682. |
Jenkins and plugins versions report
The initialization of the Prometheus plugin may cause a deadlock on startup. In a scenario where a plugin / process causes the initialization of the
DefaultPrometheusMetrics
in the boot uporg.jvnet.hudson.reactor.Reactor.runTask
, if there are pipelines running (for example resumed pipelines) then there is a chance to hit it:Deadlock details:
What Operating System are you using (both controller, and any agents involved in the problem)?
Unix
Reproduction steps
It will not always reproduce the problem, since it is a race condition, but there is a chance that it does.
Expected Results
Jenkins starts, always.
Actual Results
Jenkins sometimes nevers finish starting up because of a deadlock.
Anything else?
The DefaultPrometheusMetrics should maybe be initialized lazily.
Are you interested in contributing a fix?
Sure.
The text was updated successfully, but these errors were encountered: