---
title: stack es indices remove-block cli command
description: Remove an index block. Behaviour flags: --dry-run — validate all inputs and exit without performing any action 
url: https://www.elastic.co/elastic/docs-builder/docs/4120/reference/elastic-cli/cli/stack/es/indices/remove-block
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview
---

# stack es indices remove-block cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack es indices remove-block --index <index> --block <block> [options]
```

Remove an index block.
**Behaviour flags:**
`--dry-run` — validate all inputs and exit without performing any action

## Options

<definitions>
  <definition term="--index string required">
    A comma-separated list or wildcard expression of index names used to limit the request.
    By default, you must explicitly name the indices you are removing blocks from.
    To allow the removal of blocks from indices with `_all`, `*`, or other wildcard expressions, change the `action.destructive_requires_name` setting to `false`.
    You can update this setting in the `elasticsearch.yml` file or by using the cluster update settings API.
    **Repeatable:** pass `--index` multiple times to supply more than one value
  </definition>
  <definition term="--block enum required">
    The block type to remove from the index.
    **Values:** metadata, read, read_only, write
  </definition>
  <definition term="--allow-no-indices">
    A setting that does two separate checks on the index expression.
    If `false`, the request returns an error (1) if any wildcard expression
    (including `_all` and `*`) resolves to zero matching indices or (2) if the
    complete set of resolved indices, aliases or data streams is empty after all
    expressions are evaluated. If `true`, index expressions that resolve to no
    indices are allowed and the request returns an empty result.
  </definition>
  <definition term="--expand-wildcards enum">
    The type of index that wildcard patterns can match.
    If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams.
    It supports comma-separated values, such as `open,hidden`.
    **Values:** all, open, closed, hidden, none
    **Repeatable:** pass `--expand-wildcards` multiple times to supply more than one value
  </definition>
  <definition term="--ignore-unavailable">
    If `false`, the request returns an error if it targets a concrete (non-wildcarded)
    index, alias, or data stream that is missing, closed, or otherwise unavailable.
    If `true`, unavailable concrete targets are silently ignored.
  </definition>
  <definition term="--master-timeout string">
    The period to wait for the master node.
    If the master node is not available before the timeout expires, the request fails and returns an error.
    It can also be set to `-1` to indicate that the request should never timeout.
  </definition>
  <definition term="--timeout string">
    The period to wait for a response from all relevant nodes in the cluster after updating the cluster metadata.
    If no response is received before the timeout expires, the cluster metadata update still applies but the response will indicate that it was not completely acknowledged.
    It can also be set to `-1` to indicate that the request should never timeout.
  </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>
  <definition term="--yes">
    confirm destructive action without prompting
  </definition>
</definitions>


## Global Options

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