Skip to content

Health check stops working after node is down for some time #4

@hsanson

Description

@hsanson

If a db node drops for some period of time and then goes back and syncs again DBPinger will start giving 500 error responses even when the node is already restored.

Maybe a problem with the db connection not being re-established after losing connection the first time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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