You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2020. It is now read-only.
If multiple services are set up resulting in a circular dependency loop, they will all report as Unhealthy even if they are otherwise fully functional.
For example:
Service A => Service B => Service C => Service A
I have attached a simple solution with 3 web application projects that will cause the failure. Exploration.HeathCheck.zip
Detection of the loop would be easy enough, but deciding what action to take after detection seems like a catch 22 situation.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If multiple services are set up resulting in a circular dependency loop, they will all report as Unhealthy even if they are otherwise fully functional.
For example:
Service A => Service B => Service C => Service A
I have attached a simple solution with 3 web application projects that will cause the failure.
Exploration.HeathCheck.zip
Detection of the loop would be easy enough, but deciding what action to take after detection seems like a catch 22 situation.
The text was updated successfully, but these errors were encountered: