---
title: stack es reindex-rethrottle cli command
description: Throttle a reindex operation. Behaviour flags: --dry-run — validate all inputs and exit without performing any action 
url: https://www.elastic.co/elastic/docs-builder/docs/4118/reference/elastic-cli/cli/stack/es/reindex-rethrottle
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview
---

# stack es reindex-rethrottle cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack es reindex-rethrottle \
  --requests-per-second <requests-per-second> \
  --task-id <task-id> \
  [options]
```

Throttle a reindex operation.
**Behaviour flags:**
`--dry-run` — validate all inputs and exit without performing any action

## Options

<definitions>
  <definition term="--requests-per-second number required">
    The maximum number of documents to index per second, across the entire reindex operation (including slices).
    It can be either `-1` to turn off throttling or any decimal number like `1.7` or `12` to throttle to that level.
  </definition>
  <definition term="--task-id string required">
    The task identifier, returned when creating a reindex task, or by listing tasks via
    `GET /_reindex` or `GET /_tasks`.
    In stack, can be either the original task ID or the task ID of the relocated task.
  </definition>
  <definition term="--group-by enum">
    The way to group the tasks in the response.
    We recommend setting this to `none`, which provides the cleanest response format.
    **Values:** nodes, parents, none
  </definition>
  <definition term="--error-trace">
    When set to `true` Elasticsearch will include the full stack trace of errors
    when they occur.
  </definition>
  <definition term="--filter-path string">
    Comma-separated list of filters in dot notation which reduce the response
    returned by Elasticsearch.
    **Repeatable:** pass `--filter-path` multiple times to supply more than one value
  </definition>
  <definition term="--human">
    When set to `true` will return statistics in a format suitable for humans.
    For example `"exists_time": "1h"` for humans and
    `"exists_time_in_millis": 3600000` for computers. When disabled the human
    readable values will be omitted. This makes sense for responses being consumed
    only by machines.
  </definition>
  <definition term="--pretty">
    If set to `true` the returned JSON will be "pretty-formatted". Only use
    this option for debugging only.
  </definition>
  <definition term="--input-file string">
    path to a JSON file to use as command input
  </definition>
  <definition term="--dry-run">
    validate all inputs and exit without performing any action (preview changes without applying them)
  </definition>
</definitions>


## Global Options

<definitions>
  <definition term="--json">
    output as JSON
  </definition>
</definitions>