open-consul/website/content/commands/exec.mdx

83 lines
3.0 KiB
Plaintext
Raw Normal View History

2014-09-01 22:03:37 +00:00
---
layout: commands
2020-04-07 18:55:19 +00:00
page_title: 'Commands: Exec'
sidebar_title: exec
2020-04-07 18:55:19 +00:00
description: >-
The exec command provides a mechanism for remote execution. For example, this
can be used to run the `uptime` command across all machines providing the
`web` service.
2014-09-01 22:03:37 +00:00
---
# Consul Exec
Command: `consul exec`
The `exec` command provides a mechanism for remote execution. For example,
2014-09-01 22:03:37 +00:00
this can be used to run the `uptime` command across all machines providing
the `web` service.
Remote execution works by specifying a job, which is stored in the KV store.
Agents are informed about the new job using the [event system](/commands/event),
2020-04-09 23:46:54 +00:00
which propagates messages via the [gossip protocol](/docs/internals/gossip).
2014-09-01 22:03:37 +00:00
As a result, delivery is best-effort, and there is **no guarantee** of execution.
While events are purely gossip driven, remote execution relies on the KV store
as a message broker. As a result, the `exec` command will not be able to
properly function during a Consul outage.
**Verbose output warning:** use care to make sure that your command does not
produce a large volume of output. Writes to the KV store for this output go
2016-02-10 00:37:06 +00:00
through the Consul servers and the Raft consensus algorithm, so having a large
number of nodes in the cluster flow a large amount of data through the KV store
could make the cluster unavailable.
2020-04-09 23:20:00 +00:00
The table below shows the [required ACLs](/api#authentication) in order to
execute this command.
| ACL Required | Scope |
2020-04-07 18:55:19 +00:00
| --------------- | ----------------- |
| `agent:read` | local agent |
| `session:write` | local agent |
| `key:write` | `"_rexec"` prefix |
| `event:write` | `"_rexec"` prefix |
2014-09-01 22:03:37 +00:00
## Usage
Usage: `consul exec [options] [-|command...]`
The only required option is a command to execute. This is either given
as trailing arguments, or by specifying `-`; STDIN will be read to
2014-09-01 22:03:37 +00:00
completion as a script to evaluate.
#### API Options
2014-09-01 22:03:37 +00:00
2020-04-07 18:55:19 +00:00
@include 'http_api_options_client.mdx'
2020-04-07 23:56:08 +00:00
2020-04-07 18:55:19 +00:00
@include 'http_api_options_server.mdx'
2014-09-01 22:03:37 +00:00
#### Command Options
2014-09-01 22:03:37 +00:00
2020-04-07 18:55:19 +00:00
- `-prefix` - Key prefix in the KV store to use for storing request data.
Defaults to `_rexec`.
2014-09-01 22:03:37 +00:00
2020-04-07 18:55:19 +00:00
- `-node` - Regular expression to filter nodes which should evaluate the event.
2014-09-01 22:03:37 +00:00
2020-04-07 18:55:19 +00:00
- `-service` - Regular expression to filter to only nodes with matching services.
2014-09-01 22:03:37 +00:00
2020-04-07 18:55:19 +00:00
- `-shell` - Optional, use a shell to run the command. The default value is true.
2020-04-07 18:55:19 +00:00
- `-tag` - Regular expression to filter to only nodes with a service that has
2014-09-01 22:03:37 +00:00
a matching tag. This must be used with `-service`. As an example, you may
do `-service mysql -tag secondary`.
2014-09-01 22:03:37 +00:00
2020-04-07 18:55:19 +00:00
- `-wait` - Specifies the period of time in which no agent's respond before considering
2014-09-01 22:03:37 +00:00
the job finished. This is basically the quiescent time required to assume completion.
This period is not a hard deadline, and the command will wait longer depending on
various heuristics.
2020-04-07 18:55:19 +00:00
- `-wait-repl` - Period to wait after writing the job specification for replication.
2014-09-01 22:03:37 +00:00
This is a heuristic value and enables agents to do a stale read of the job. Defaults
to 200 msec.
2014-09-01 22:03:37 +00:00
2020-04-07 18:55:19 +00:00
- `-verbose` - Enables verbose output.