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

Enhancement: Asynchronous Scheduled Health Indicators #5910

Closed
mgerlach opened this issue May 10, 2016 · 1 comment
Closed

Enhancement: Asynchronous Scheduled Health Indicators #5910

mgerlach opened this issue May 10, 2016 · 1 comment
Labels
status: duplicate A duplicate of another issue

Comments

@mgerlach
Copy link

Hi,

running on spring-boot 1.3.3, we experienced a hanging GET /health when one dependency was down, e. g. a Mongo client running into a 10s timeout (because the MongoDB server was down).

The expected /health result would have been an immediate DOWN or UNKNOWN, but instead the page did not load for 10s.

We thought that if health checks are based on non-interruptible synchronous I/O, they'd be better executed periodically in the background with the most recent results cached with some TTL.

The idea would be to mark HealthIndicator implementations somehow (annotation, marker interface...) and have the framework handle the scheduling and caching. Cache ttl and schedule frequency (where schedule frequency should be less than the ttl otherwise the cache may be empty which would have to be reported as UNKNOWN) could be made configurable per check or globally.

It would also be cool if the built-in (autoconfigured) HealthIndicators could be configured to be async.

Is any such feature on the road map or does anyone have other ideas on solving that problem generically?

Cheers
Martin

@mgerlach mgerlach changed the title Enhancement: Asynchronous Scheduled Health Checks Enhancement: Asynchronous Scheduled Health Indicators May 10, 2016
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label May 10, 2016
@wilkinsona
Copy link
Member

Duplicates #2652

@wilkinsona wilkinsona added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged labels May 10, 2016
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