Skip to content

Improve liveness/readiness check #643

@arkbriar

Description

@arkbriar

Issue found in the PR #642 (comment)

A possible solution is

The problem is caused by the slow compute readiness, which relies on the meta to be ready first and the k8s setup the DNS. After compute connects to the meta, it then starts its server. I think the best solutions is to use a separate port for health check of compute/compactor nodes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions