mirror of https://github.com/status-im/consul.git
Updating maint.html to remove node maint (#3354)
* Updating maint.html to remove node maint as discussed in #3268 maint mode does not have any affect on the node health. * Update maint.html.markdown.erb
This commit is contained in:
parent
c8f35bf6be
commit
93ea4d66d2
|
@ -10,14 +10,14 @@ description: >
|
||||||
|
|
||||||
Command: `consul maint`
|
Command: `consul maint`
|
||||||
|
|
||||||
The `maint` command provides control of both service and node maintenance mode.
|
The `maint` command provides control of service maintenance mode.
|
||||||
Using the command, it is possible to mark a service provided by a node or the
|
Using the command, it is possible to mark a service provided by a node or all the services on the
|
||||||
node as a whole as "under maintenance". In this mode of operation, the service
|
node as a whole as "under maintenance". In this mode of operation, the service
|
||||||
or node will not appear in DNS query results, or API results. This effectively
|
will not appear in DNS query results, or API results. This effectively
|
||||||
takes the service or node out of the pool of available "healthy" nodes.
|
takes the service out of the pool of available "healthy" nodes of a service.
|
||||||
|
|
||||||
Under the hood, maintenance mode is activated by registering a health check in
|
Under the hood, maintenance mode is activated by registering a health check in
|
||||||
critical status against a node or service, and deactivated by deregistering the
|
critical status against a service, and deactivated by deregistering the
|
||||||
health check.
|
health check.
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
@ -30,19 +30,17 @@ Usage: `consul maint [options]`
|
||||||
|
|
||||||
#### Command Options
|
#### Command Options
|
||||||
|
|
||||||
* `-enable` - Enable maintenance mode on a given service or node. If
|
* `-enable` - Enable maintenance mode on all services on a node. If
|
||||||
combined with the `-service` flag, we operate on a specific service ID.
|
combined with the `-service` flag, we operate on a specific service ID.
|
||||||
Otherwise, node maintenance mode is enabled.
|
|
||||||
|
|
||||||
* `-disable` - Disable maintenance mode on a given service or node. If
|
* `-disable` - Disable maintenance mode on all service on a node. If
|
||||||
combined with the `-service` flag, we operate on a specific service ID.
|
combined with the `-service` flag, we operate on a specific service ID.
|
||||||
Otherwise, node maintenance mode is disabled.
|
|
||||||
|
|
||||||
* `-reason` - An optional reason for placing the node or service into
|
* `-reason` - An optional reason for placing the service into
|
||||||
maintenance mode. If provided, this reason will be visible in the newly-
|
maintenance mode. If provided, this reason will be visible in the newly-
|
||||||
registered critical check's "Notes" field.
|
registered critical check's "Notes" field.
|
||||||
|
|
||||||
* `-service` - An optional service ID to control node maintenance mode for. By
|
* `-service` - An optional service ID to control maintenance mode for a given service. By
|
||||||
providing this flag, the `-enable` and `-disable` flags functionality is
|
providing this flag, the `-enable` and `-disable` flags functionality is
|
||||||
modified to operate on the given service ID.
|
modified to operate on the given service ID.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue