Skip to content

Commit

Permalink
Update doc for the Task Worker with the new command line (#1988)
Browse files Browse the repository at this point in the history
  • Loading branch information
camsellem authored Nov 28, 2024
1 parent 563da53 commit 0770be9
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions content/docs/task-runners/03.task-runners-vs-worker-groups.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,11 +46,10 @@ Here are common use cases in which **Task Runners** can be beneficial:

### Worker Groups Usage

First, make sure you start the worker with the `--worker-group myWorkerGroupKey` flag.
First, make sure you start the worker with the `--worker-group myWorkerGroupKey` flag. It's important for the new worker to have a configuration similar to that of your principal Kestra server and to have access to the same backend database and internal storage. The configuration file will be passed via the `--config` flag, as shown in the example below.

```shell
kestra server worker --worker-group=myWorkerGroupKey \
--server=your_ee_host --api-token=your_ee_api_token
kestra server worker --worker-group=myWorkerGroupKey --config=/path/to/kestra-config.yaml
```

To assign a task to the desired worker group, simply add a `workerGroup.key` property. This will ensure that the task or polling trigger is executed on a worker in the specified worker group.
Expand Down

0 comments on commit 0770be9

Please sign in to comment.