Skip to content
This repository was archived by the owner on Jun 29, 2020. It is now read-only.
This repository was archived by the owner on Jun 29, 2020. It is now read-only.

Circular health checks dependency loops #87

Description

@Gaikotsu2

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions