hashicorp / hashicorp/consul

Node/Service Maintenance at Cluster level

Open
#9,306 0 comments 4 reactions 0 assignees View on GitHub
theme/catalog type/enhancement
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
2d 6h
Merged PRs (30d)
43

Description

#### Feature Description

An ability to mark a node or its services as *in maintenance* while the node is down, so when the node comes back in the cluster, it is still in maintenance.

#### Use Case(s)

In real hardware systems, we sometimes face downtime on specific servers without having the ability to predict when the node will be back again.

When we know in advance that a given node will need maintenance, we use service or node maintenance to evict the node from the cluster, so when it comes back, the node is not taken into account before some checks/sync are performed.

This is especially important on systems storing data (eg: databases, filers...), where some procedures need to be applied *before* the node can serve data.

This also could be applied in case of a security issue to avoid a given node to receive traffic by marking it unhealthy (without the ability to connect to the node for instance).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.