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

Limit execution time evaluating the health indicators #37068

Closed
ceremo opened this issue Aug 22, 2023 · 1 comment
Closed

Limit execution time evaluating the health indicators #37068

ceremo opened this issue Aug 22, 2023 · 1 comment
Labels
status: duplicate A duplicate of another issue

Comments

@ceremo
Copy link

ceremo commented Aug 22, 2023

The health actuator endpoint can become unresponsive if one of the health indicators gets stuck. This behavior affects the responsiveness of the health endpoint, causing it to be unresponsive until all health indicators are evaluated.

It could be beneficial to execute the health indicators asynchronously. For instance, in servlet applications, this can be achieved by evaluating the health indicator in a single-thread executor and a Future. In reactive applications, health indicators can be subscribed to using a single scheduler for the Mono created in each health indicator. In both cases, a timeout duration (property) can be established for evaluating each health indicator. In addition, it would be great if when a health indicator cannot be evaluated within the specified time, it reports an UNKNOWN status.

What's your opinion?

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 22, 2023
@snicoll
Copy link
Member

snicoll commented Aug 22, 2023

This is a duplicate of #2652, #25459, and #4391 (comment)

@snicoll snicoll closed this as not planned Won't fix, can't repro, duplicate, stale Aug 22, 2023
@snicoll snicoll added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged labels Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants