---
title: Reindex indices examples
description: The Reindex API copies documents from a source index, data stream, or alias to a destination, allowing for optional data modification through scripts...
url: https://www.elastic.co/elastic/docs-builder/docs/3466/reference/elasticsearch/rest-apis/reindex-indices
products:
  - Elasticsearch
applies_to:
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available
---

# Reindex indices examples
The [Reindex API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-reindex) copies documents from a source index, data stream, or alias to a destination, allowing for optional data modification through scripts or ingest pipelines.
You can learn how to:
**Run and control reindexing**
- [Basic reindexing example](#basic-reindexing-example)
- [Reindex asynchronously](#docs-reindex-task-api)
- [Reindex multiple indices sequentially](#docs-reindex-multiple-sequentially)
- [Reindex from multiple indices in a single request](#docs-reindex-multiple-sources)
- [Reindex with throttling](#docs-reindex-throttle)
- [Reindex with rethrottling](#docs-reindex-rethrottle)
- [Reindex with slicing](#docs-reindex-slice)

**Filter and transform documents**
- [Reindex selected documents with a query](#docs-reindex-select-query)
- [Reindex a limited number of documents with `max_docs`](#docs-reindex-select-max-docs)
- [Reindex selected fields](#docs-reindex-filter-source)
- [Reindex to change the name of a field](#docs-reindex-change-name)
- [Modify documents during reindexing](#reindex-scripts)
- [Extract a random subset of the source](#docs-reindex-api-subset)
- [Reindex daily indices](#docs-reindex-daily-indices)

**Route or send data elsewhere**
- [Reindex with custom routing](#docs-reindex-routing)
- [Reindex with an ingest pipeline](#reindex-with-an-ingest-pipeline)
- [Reindex from remote](#reindex-from-remote)
- [Reindex in cross-project search](#reindex-cps)

**Troubleshooting**
- [Manage asynchronous reindex operations](#monitor-reindex-tasks)
- [Diagnose node failures](#diagnose-node-failures)
- [Version conflicts](#version-conflicts)


## Basic reindexing example

Use the Reindex API to copy all documents from one index to another.
```json

{
  "source": {
    "index": "my-index-000001"
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}
```


## Reindex asynchronously

If the request contains `wait_for_completion=false`, Elasticsearch performs some preflight checks, launches the request, and returns a `task` ID you can use to [manage](#monitor-reindex-tasks) the operation.
For long-running reindexes, prefer asynchronous reindexes. Synchronous reindex keeps a client waiting on the node that received the request and this will time out.

## Reindex multiple indices sequentially

If you have many sources to reindex it is generally better to reindex them one at a time rather than using a glob pattern to pick up multiple sources.
That way you can resume the process if there are any errors by removing the partially completed source and starting over.
It also makes parallelizing the process straightforward: split the list of sources to reindex and run each list in parallel.
One-off bash scripts seem to work nicely for this:
```bash
for index in i1 i2 i3 i4 i5; do
  curl -HContent-Type:application/json -XPOST localhost:9200/_reindex?pretty -d'{
    "source": {
      "index": "'$index'"
    },
    "dest": {
      "index": "'$index'-reindexed"
    }
  }'
done
```


## Reindex with throttling

Set `requests_per_second` to any positive decimal number (for example, `1.4`, `6`, or `1000`) to throttle the rate at which the reindex API issues batches of index operations.
Requests are throttled by padding each batch with a wait time.
To turn off throttling, set `requests_per_second` to `-1`.
The throttling is done by waiting between batches.
Set the underlying search keep-alive long enough that a slower batch does not expire the context before the next read.
<admonition title="Scroll query parameter versus PIT keep-alive">
  <applies-switch>
    <applies-item title="{ "stack": "ga 9.5+", "serverless": "ga" }" applies-to="Elastic Cloud Serverless: Generally available, Elastic Stack: Planned">
      Reindex reads the source with point-in-time pagination for local reindexes and for reindex from remote when the remote cluster is Elasticsearch 7.10 or later (so a PIT can be opened there). Use [`cluster.reindex.pit.keep_alive`](/elastic/docs-builder/docs/3466/reference/elasticsearch/configuration-reference/index-management-settings#reindex-settings) to change how long those contexts stay open. The top-level `scroll` parameter on the reindex request has no effect on that path.Reindex from a remote cluster older than Elasticsearch 7.10 cannot use the PIT path and falls back to scroll. The `scroll` parameter then sets scroll keep-alive.
    </applies-item>

    <applies-item title="{ "stack": "ga 9.0-9.4" }" applies-to="Elastic Stack: Generally available from 9.0 to 9.4">
      Reindex uses scroll-based pagination for local and remote sources. The `scroll` parameter sets scroll keep-alive.
    </applies-item>
  </applies-switch>
</admonition>

The padding time is the difference between the batch size divided by the `requests_per_second` and the time spent writing.
By default, the batch size is `1000`, so if `requests_per_second` is set to `500`:
```txt
target_time = 1000 / 500 per second = 2 seconds
wait_time = target_time - write_time = 2 seconds - .5 seconds = 1.5 seconds
```

Since the batch is issued as a single `_bulk` request, large batch sizes cause Elasticsearch to create many requests and then wait for a while before starting the next set. This is "bursty" instead of "smooth".

## Reindex with rethrottling

The value of `requests_per_second` can be changed on a running reindex using the `_rethrottle` API. For example:
```json
```

Use the `task` ID returned from the call to `POST _reindex` or find it using the [management](#monitor-reindex-tasks) APIs.
Like when setting it on the Reindex API, `requests_per_second` can be either `-1` to turn off throttling or any decimal number like `1.7` or `12` to throttle to that level.
Rethrottling that speeds up the query takes effect immediately, but rethrottling that slows down the query will take effect after completing the current batch.
This prevents the underlying search context used between batches from timing out.
The same `scroll` versus point-in-time keep-alive rules apply. Refer to the note under [Reindex with throttling](#docs-reindex-throttle).

## Reindex with slicing

Reindex supports [sliced search](/elastic/docs-builder/docs/3466/reference/elasticsearch/rest-apis/paginate-search-results#slice-scroll) to parallelize the reindexing process.
This parallelization can improve efficiency and provide a convenient way to break the request down into smaller parts.
<note>
  Reindexing from remote clusters does not support manual or automatic slicing.
</note>


### Reindex with manual slicing

Slice a reindex request manually by providing a slice id and total number of slices to each request:
```json

{
  "source": {
    "index": "my-index-000001",
    "slice": {
      "id": 0,
      "max": 2
    }
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}

{
  "source": {
    "index": "my-index-000001",
    "slice": {
      "id": 1,
      "max": 2
    }
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}
```

You can verify this works by:
```json
```

which results in a sensible `total` like this one:
```json
{
  "hits": {
    "total" : {
        "value": 120,
        "relation": "eq"
    }
  }
}
```


### Reindex with automatic slicing

You can also let the reindex API automatically parallelize using [sliced search](/elastic/docs-builder/docs/3466/reference/elasticsearch/rest-apis/paginate-search-results#slice-scroll) to slice on `_id`.
Use `slices` to specify the number of slices to use:
```json

{
  "source": {
    "index": "my-index-000001"
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}
```

You can also verify this works by:
```json
```

which results in a sensible `total` like this one:
```json
{
  "hits": {
    "total" : {
        "value": 120,
        "relation": "eq"
    }
  }
}
```

Setting `slices` to `auto` will let Elasticsearch choose the number of slices to use.
This setting will use one slice per shard, up to a certain limit.
If there are multiple sources, it will choose the number of slices based on the index or backing index with the smallest number of shards.
Adding `slices` to the reindex API automates the manual process used in the preceding section, creating sub-requests which means it has some quirks:
- <applies-to>Elastic Stack: Generally available</applies-to> You can view these requests in the [task management APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks). These sub-requests are "child" tasks of the task for the request with `slices`.
- Fetching the status of the task for the request with `slices` only contains the status of completed slices.
- These sub-requests are individually addressable for things like cancellation and rethrottling.
- Rethrottling the request with `slices` will rethrottle the unfinished sub-request proportionally.
- Canceling the request with `slices` will cancel each sub-request.
- Due to the nature of `slices` each sub-request won't get a perfectly even portion of the documents. All documents will be addressed, but some slices might be larger than others. Expect larger slices to have a more even distribution.
- Parameters like `requests_per_second` and `max_docs` on a request with `slices` are distributed proportionally to each sub-request. Combine that with the point above about distribution being uneven and you should conclude that using `max_docs` with `slices` might not result in exactly `max_docs` documents being reindexed.
- Each sub-request gets a slightly different snapshot of the source, though these are all taken at approximately the same time.


### Picking the number of slices

If slicing automatically, setting `slices` to `auto` will choose a reasonable number for most indices. If slicing manually or otherwise tuning automatic slicing, use these guidelines.
Query performance is most efficient when the number of `slices` is equal to the number of shards in the index. If that number is large (for example, 500), choose a lower number as too many `slices` will hurt performance. Setting `slices` higher than the number of shards generally does not improve efficiency and adds overhead.
Indexing performance scales linearly across available resources with the number of slices.
Whether query or indexing performance dominates the runtime depends on the documents being reindexed and cluster resources.

## Reindex with custom routing

By default if the reindex API sees a document with routing then the routing is preserved unless it's changed by the script. You can set `routing` on the `dest` request to change this.
For example:
<definitions>
  <definition term="keep">
    Sets the routing on the bulk request sent for each match to the routing on the match. This is the default value.
  </definition>
  <definition term="discard">
    Sets the routing on the bulk request sent for each match to `null`.
  </definition>
  <definition term="=<some text>">
    Sets the routing on the bulk request sent for each match to all text after the `=`.
  </definition>
</definitions>

You can use the following request to copy all documents from the `source` with the company name `cat` into the `dest`  with routing set to `cat`:
```json

{
  "source": {
    "index": "source",
    "query": {
      "match": {
        "company": "cat"
      }
    }
  },
  "dest": {
    "index": "dest",
    "routing": "=cat"
  }
}
```

By default the reindex API reads the source in batches of 1000 documents. The same batch size applies whether the run uses scroll-based or point-in-time pagination. You can change it with the `size` field in the `source` element:
```json

{
  "source": {
    "index": "source",
    "size": 100
  },
  "dest": {
    "index": "dest",
    "routing": "=cat"
  }
}
```


## Reindex with an ingest pipeline

Reindex can also use the [ingest pipelines](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3466/manage-data/ingest/transform-enrich/ingest-pipelines) feature by specifying a `pipeline` like this:
```json

{
  "source": {
    "index": "source"
  },
  "dest": {
    "index": "dest",
    "pipeline": "some_ingest_pipeline"
  }
}
```


## Reindex selected documents with a query

You can limit the documents by adding a query to the `source`. For example, the following request only copies documents with a `user.id` of `kimchy` into `my-new-index-000001`:
```json

{
  "source": {
    "index": "my-index-000001",
    "query": {
      "term": {
        "user.id": "kimchy"
      }
    }
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}
```


## Reindex a limited number of documents with `max_docs`

You can limit the number of processed documents by setting `max_docs`.
For example, this request copies a single document from `my-index-000001` to `my-new-index-000001`:
```json

{
  "max_docs": 1,
  "source": {
    "index": "my-index-000001"
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}
```


## Reindex from multiple indices in a single request

The `index` attribute in `source` can be a list, allowing you to copy from lots of sources in one request.
This will copy documents from the `my-index-000001` and `my-index-000002` indices:
```json

{
  "source": {
    "index": ["my-index-000001", "my-index-000002"]
  },
  "dest": {
    "index": "my-new-index-000002"
  }
}
```

<note>
  The reindex API makes no effort to handle ID collisions so the last document written will "win" but the order isn't usually predictable so it is not a good idea to rely on this behavior. Instead, make sure that IDs are unique using a script.
</note>


## Reindex selected fields

You can use source filtering to reindex a subset of the fields in the original documents.
For example, the following request only reindexes the `user.id` and `_doc` fields of each document:
```json

{
  "source": {
    "index": "my-index-000001",
    "_source": ["user.id", "_doc"]
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}
```


## Reindex to change the name of a field

The reindex API can be used to build a copy of an index with renamed fields.
Say you create an index containing documents that look like this:
```json

{
  "text": "words words",
  "flag": "foo"
}
```

If you don't like the name `flag` and want to replace it with `tag`, the reindex API can create the other index for you:
```json

{
  "source": {
    "index": "my-index-000001"
  },
  "dest": {
    "index": "my-new-index-000001"
  },
  "script": {
    "source": "ctx._source.tag = ctx._source.remove(\"flag\")"
  }
}
```

Now you can get the new document:
```json
```

The response is:
```json
{
  "found": true,
  "_id": "1",
  "_index": "my-new-index-000001",
  "_version": 1,
  "_seq_no": 44,
  "_primary_term": 1,
  "_source": {
    "text": "words words",
    "tag": "foo"
  }
}
```


## Reindex daily indices

You can use the reindex API in combination with [Painless](https://www.elastic.co/elastic/docs-builder/docs/3466/reference/scripting-languages/painless/painless) to reindex daily indices to apply a new template to the existing documents.
Assuming you have indices that contain documents like:
```json

{"system.cpu.idle.pct": 0.908}

{"system.cpu.idle.pct": 0.105}
```

The new template for the `metricbeat-*` indices is already loaded into Elasticsearch, but it applies only to the newly created indices. Painless can be used to reindex the existing documents and apply the new template.
The script below extracts the date from the index name and creates a new index with `-1` appended. All data from `metricbeat-2016.05.31` will be reindexed into `metricbeat-2016.05.31-1`.
```json

{
  "source": {
    "index": "metricbeat-*"
  },
  "dest": {
    "index": "metricbeat"
  },
  "script": {
    "lang": "painless",
    "source": "ctx._index = 'metricbeat-' + (ctx._index.substring('metricbeat-'.length(), ctx._index.length())) + '-1'"
  }
}
```

All documents from the previous metricbeat indices can now be found in the `*-1` indices.
```json
```

The previous method can also be used in conjunction with [changing a field name](#docs-reindex-change-name) to load only the existing data into the new index and rename any fields if needed.

## Extract a random subset of the source

The reindex API can be used to extract a random subset of the source for testing:
```json

{
  "max_docs": 10,
  "source": {
    "index": "my-index-000001",
    "query": {
      "function_score" : {
        "random_score" : {},
        "min_score" : 0.9    <1>
      }
    }
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}
```


## Modify documents during reindexing

Like `_update_by_query`, the reindex API supports a script that modifies the document.
Unlike `_update_by_query`, the script is allowed to modify the document's metadata.
This example bumps the version of the source document:
```json

{
  "source": {
    "index": "my-index-000001"
  },
  "dest": {
    "index": "my-new-index-000001",
    "version_type": "external"
  },
  "script": {
    "source": "if (ctx._source.foo == 'bar') {ctx._version++; ctx._source.remove('foo')}",
    "lang": "painless"
  }
}
```

As in `_update_by_query`, you can set `ctx.op` to change the operation that is run on the destination:
<definitions>
  <definition term="noop">
    Set `ctx.op = "noop"` if your script decides that the document doesn't have to be indexed in the destination. This no operation will be reported in the `noop` counter in the response body.
  </definition>
  <definition term="delete">
    Set `ctx.op = "delete"` if your script decides that the document must be deleted from the destination. The deletion will be reported in the `deleted` counter in the response body.
  </definition>
</definitions>

Setting `ctx.op` to anything other than `noop` or `delete` will result in an error. Similarly, modifying other fields in `ctx` besides `_id`, `_index`, `_version`, and `_routing` will also fail.
Be careful that you can change:
- `_id`
- `_index`
- `_version`
- `_routing`

Setting `_version` to `null` or clearing it from the `ctx` map is like not sending the version in an indexing request. It will cause the document to be overwritten in the destination regardless of the version on the target or the version type you use in the reindex API request.

## Reindex from remote

<applies-to>
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available
</applies-to>

Reindex supports reindexing from a remote Elasticsearch cluster:
```json

{
  "source": {
    "remote": {
      "host": "<OTHER_HOST_URL>",
      "username": "user",
      "password": "pass"
    },
    "index": "my-index-000001",
    "query": {
      "match": {
        "test": "data"
      }
    }
  },
  "dest": {
    "index": "my-new-index-000001"
  }
}
```

The `host` parameter must contain a scheme, host, port (for example, `https://<OTHER_HOST_URL>:9200`), and optional path (for example, `https://<OTHER_HOST_URL>:9200/proxy`).

### Using basic auth

To authenticate with the remote cluster using basic auth, set the `username` and `password` parameters, as in the preceding example.
Be sure to use `https` when using basic auth, or the password will be sent in plain text. There are a [range of settings](#reindex-ssl) available to configure the behavior of the `https` connection.

### Using an API key

It is also possible (and encouraged) to authenticate with the remote cluster through the use of a valid API key:
<applies-switch>
  <applies-item title="{ "stack": "ga 9.3+", "serverless": "ga" }" applies-to="Elastic Cloud Serverless: Generally available, Elastic Stack: Generally available since 9.3">
    ```json

    {
      "source": {
        "remote": {
          "host": "<OTHER_HOST_URL>",
          "api_key": "<API_KEY_VALUE>"
        },
        "index": "my-index-000001",
        "query": {
          "match": {
            "test": "data"
          }
        }
      },
      "dest": {
        "index": "my-new-index-000001"
      }
    }
    ```
  </applies-item>

  <applies-item title="{ "stack": "ga 9.0-9.2" }" applies-to="Elastic Stack: Generally available from 9.0 to 9.2">
    ```json

    {
      "source": {
        "remote": {
          "host": "<OTHER_HOST_URL>",
          "headers": {
            "Authorization": "<API_KEY_VALUE>"
          }
        },
        "index": "my-index-000001",
        "query": {
          "match": {
            "test": "data"
          }
        }
      },
      "dest": {
        "index": "my-new-index-000001"
      }
    }
    ```
  </applies-item>
</applies-switch>

Be sure to use `https` when using an API key, or it will be sent in plain text. There are a [range of settings](#reindex-ssl) available to configure the behavior of the `https` connection.

### Permitted remote hosts

The remote hosts that you can use depend on whether you're using the versioned Elastic Stack or Serverless.
- In the versioned Elastic Stack, remote hosts have to be explicitly allowed in elasticsearch.yml using the `reindex.remote.whitelist` property. It can be set to a comma-delimited list of allowed remote host and port combinations. Scheme is ignored; only the host and port are used. For example:
  ```
  reindex.remote.whitelist: ["otherhost:9200", "another:9200", "127.0.10.*:9200", "localhost:*"]
  ```
  The list of allowed hosts must be configured on any node that will coordinate the reindex.
- In Elastic Cloud Serverless, all remote hosts in any Elastic Cloud region are allowed, including Elastic Cloud Hosted deployments and Serverless projects.


### Compatibility

This feature should work with remote clusters of any version of Elasticsearch you are likely to find. This should allow you to upgrade from any version of Elasticsearch to the current version by reindexing from a cluster of the old version.
<warning>
  Elasticsearch does not support forward compatibility across major versions. For example, you cannot reindex from a 7.x cluster into a 6.x cluster.
</warning>

To enable queries sent to earlier versions of Elasticsearch the `query` parameter is sent directly to the remote host without validation or modification.
<note>
  Reindexing from remote clusters does not support manual or automatic slicing.
</note>


### Tuning parameters

Reindexing from a remote server uses an on-heap buffer that defaults to a maximum size of 100mb.
If the remote index includes very large documents you'll need to use a smaller batch size.
The following example sets the batch size to `10` which is very, very small.
```json

{
  "source": {
    "remote": {
      "host": "<OTHER_HOST_URL>",
      ...
    },
    "index": "source",
    "size": 10,
    "query": {
      "match": {
        "test": "data"
      }
    }
  },
  "dest": {
    "index": "dest"
  }
}
```

It is also possible to set the socket read timeout on the remote connection with the `socket_timeout` field and the connection timeout with the `connect_timeout` field.
Both default to 30 seconds.
This example sets the socket read timeout to one minute and the connection timeout to 10 seconds:
```json

{
  "source": {
    "remote": {
      "host": "<OTHER_HOST_URL>",
      ...,
      "socket_timeout": "1m",
      "connect_timeout": "10s"
    },
    "index": "source",
    "query": {
      "match": {
        "test": "data"
      }
    }
  },
  "dest": {
    "index": "dest"
  }
}
```


### Configuring SSL parameters

Reindex from remote supports configurable SSL settings.
These must be specified in the `elasticsearch.yml` file, except for the secure settings, which you add in the Elasticsearch keystore.
You cannot configure SSL in the body of the reindex API request.
Refer to [Reindex settings](/elastic/docs-builder/docs/3466/reference/elasticsearch/configuration-reference/index-management-settings#reindex-settings).

## Reindex in cross-project search

<applies-to>
  - Elastic Cloud Serverless: Preview
</applies-to>

When [cross-project search](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3466/explore-analyze/cross-project-search) is enabled, the [Reindex API](https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-reindex) can pull documents from indices across linked Serverless projects.
The `source.index` field resolves across the origin project and all its linked projects.
You can narrow the scope of the source using [project routing](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3466/explore-analyze/cross-project-search/cross-project-search-project-routing) or [qualified index expressions](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3466/explore-analyze/cross-project-search/cross-project-search-search#search-expressions).
Documents are always written to the destination index on the origin project.
There are two ways to use reindex to move data between Serverless projects in CPS:
- [**Reindex across linked projects**](#reindex-cps-linked): reindex from the origin project and its [linked projects](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3466/explore-analyze/deploy-manage/cross-project-search-config/cps-config-link-and-manage).
- [**Reindex from a remote project**](#reindex-cps-remote): reindex from another Serverless project or an Elastic Cloud Hosted deployment by connecting over HTTP with `source.remote.host`.


### Reindex across linked projects

When not using [`source.remote`](#reindex-cps-remote), the Reindex API pulls documents from the origin project and its linked projects:
- Only the origin project and projects [linked](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3466/explore-analyze/deploy-manage/cross-project-search-config/cps-config-link-and-manage) to it can be targeted.
- The `source.index` field resolves across the origin project and all linked projects.
- You can use `project_routing` in the `source` section to limit which projects are included.
- Qualified index expressions (for example, `project1:logs`) are supported.

The following request reindexes documents from the `logs` index, limiting the source to the linked project with alias `project1`:
```json

{
  "source": {
    "project_routing": "_alias:project1",
    "index": "logs"
  },
  "dest": {
    "index": "new_index"
  }
}
```


### Reindex from a remote project

When using `source.remote.host`, you can reindex from another Serverless project or an Elastic Cloud Hosted deployment over HTTP.
By default, the reindex operation pulls documents only from the specified remote target.
If the remote target is a cross-project search-enabled Serverless project, the `source.index` field can also resolve across the remote project and all its linked projects. For this to work, the request must authenticate with an [Elastic Cloud API key](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3466/deploy-manage/api-keys/elastic-cloud-api-keys) that has **Cloud, Elasticsearch, and Kibana API** access. An [Elasticsearch API key](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3466/deploy-manage/api-keys/elasticsearch-api-keys) only provides access to the remote project itself, not its linked projects.
The following request reindexes documents from the `logs` index on a remote project. The source targets the `logs` index on the remote project and any of its linked projects, but not the `logs` index on the origin project (the project you sent the reindex request to):
```json

{
  "source": {
    "remote": {
      "host": "https://my-remote-project.es.us-east-1.aws.elastic.cloud:443",
      "api_key": "<API_KEY>"
    },
    "index": "logs"
  },
  "dest": {
    "index": "new_index"
  }
}
```

You can add `project_routing` to the `source` section to limit which of the remote project's linked projects are included. The following request limits the reindex source to the remote project's origin project only:
```json

{
  "source": {
    "remote": {
      "host": "https://my-remote-project.es.us-east-1.aws.elastic.cloud:443",
      "api_key": "<API_KEY>"
    },
    "project_routing": "_alias:_origin",
    "index": "logs"
  },
  "dest": {
    "index": "new_index"
  }
}
```

<note>
  `project_routing` is only supported when the remote target is a Serverless project. If you include `project_routing` in a request targeting a non-Serverless deployment, the request returns an error.
</note>


## Manage asynchronous reindex operations

<applies-switch>
  <applies-item title="{ "stack": "ga 9.5+", "serverless": "ga" }" applies-to="Elastic Cloud Serverless: Generally available, Elastic Stack: Planned">
    When run asynchronously with `wait_for_completion=false`, a reindex operation can be managed with the reindex management API, using the `task` ID returned from the `POST _reindex` call:
    ```json
    ```

    <note>
      - If the `completed` field in the response to the `GET _reindex/<id>` call is `false` then the reindex is still running.
      - If the `completed` field is `true` and the `error` field is present then the reindex failed. Check the `error` object for details.
      - If the `completed` field is `true` and the `response` field is present then the reindex at least partially succeeded. Check the `failures` field in the `response` object to see if there were partial failures.
      - If this call returns a 404 (`NOT FOUND`), then Elasticsearch could not resolve a running or stored completed operation for that ID.
      When a reindex fails, completes with failures in the response, or returns 404 and cannot be tracked further, partial data might have been written to the destination index.
    </note>
    To view all currently running reindex operations:
    ```json
    ```
    To cancel a running reindex operation:
    ```json
    ```
  </applies-item>

  <applies-item title="{ "stack": "ga 9.0-9.4" }" applies-to="Elastic Stack: Generally available from 9.0 to 9.4">
    When run asynchronously with `wait_for_completion=false`, a reindex task can be managed with the task management API, using the `task` ID returned from the `POST _reindex` call:
    ```json
    ```

    <note>
      - If the `completed` field in the response to the `GET _tasks/<task_id>` call is `false` then the reindex is still running.
      - If the `completed` field is `true` and the `error` field is present then the reindex failed. Check the `error` object for details.
      - If the `completed` field is `true` and the `response` field is present then the reindex at least partially succeeded. Check the `failures` field in the `response` object to see if there were partial failures.
      - If this call returns a 404 (`NOT FOUND`), then Elasticsearch could not resolve a running or stored completed task for that task ID.
      When a reindex fails, completes with failures in the response, or returns 404 and cannot be tracked further, partial data might have been written to the destination index.
    </note>
    To view all currently running reindex tasks (where this API is available):
    ```json
    ```
    To cancel a running reindex task (where this API is available):
    ```json
    ```
    If this API is not available, you can achieve a similar effect by deleting the
    target index:
    ```json
    ```
    This will cause the reindex task to fail with a `index_not_found_exception`
    error.
  </applies-item>
</applies-switch>


## Diagnose node failures

Node crashes can sometimes be caused by insufficient disk space. To check disk allocation across your cluster:
```json
```


## Version conflicts

By default, version conflicts stop the reindexing process.
To continue reindexing in the case of conflicts, set `conflicts` to `proceed`.
This might be necessary when retrying a failed reindex operation, as the destination index could be left in a partial state.
```json

{
  "source": {
    "index": "my-index-000001"
  },
  "dest": {
    "index": "my-new-index-000001",
    "op_type": "create"
  },
  "conflicts": "proceed"
}
```