lbcli disable server
Disables a server from the cluster into maintenance mode.
This operation can only be invoked for a server that is in Active state, and cannot be invoked while a server is being upgraded. Disabling a server operation that will lead to risk of service loss will be failed by default. To force disabling a server, even if it may lead to risk of service loss, use the --force flag.
lbcli disable server [UUID|NAME] [flags]Examples:
x
# Disable a server with UUID 302e7970-b138-11e9-91d4-525401643394.lbcli disable server --uuid=302e7970-b138-11e9-91d4-525401643394# Disable a server and set server specific permanent failure timeout.lbcli disable server --uuid=302e7970-b138-11e9-91d4-525401643394 --permanent-failure-timeout=8h| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
| --help | -h | bool | Help for server. | |
| --name | string | Server name (required if UUID is not given). | ||
| --uuid | string | Server UUID (required if name is not given). | ||
| --force | bool | Force disable, bypass risk of service loss checks (optional) Default: false. | ||
| --evict-data | bool | Evict data from the server (optional, default: false). Note: This is a technology preview; it should not be used in production. | ||
| --permanent-failure-timeout | string | Set a server-specific permanent failure timeout of 1 hour or more. Use a decimal value followed by a unit (ns, us, ms, s, m, h); e.g., 1h1m, 2h. Use 0 for infinite timeout (optional, default: empty). |
This is an async operation. It can be applied on an enabled server, and not during an ongoing upgrade operation.
Was this page helpful?