Reindex
editReindex
editactions:
1:
description: "Reindex index1 into index2"
action: reindex
options:
wait_interval: 9
max_wait: -1
request_body:
source:
index: index1
dest:
index: index2
filters:
- filtertype: none
There are many options for the reindex option. The best place to start is in the request_body documentation to see how to configure this action. All other options are as follows.
Required settings
editOptional settings
edit- refresh
- remote_aws_key
- remote_remote_aws_region
- remote_aws_secret_key
- remote_certificate
- remote_client_cert
- remote_client_key
- remote_filters
- remote_ssl_no_validate
- remote_url_prefix
- request_body
- requests_per_second
- slices
- timeout
- wait_for_active_shards
- wait_for_completion
- max_wait
- wait_interval
- ignore_empty_list
- timeout_override
- continue_if_exception
- disable_action
- migration_prefix
- migration_suffix
See an example of this action in an actionfile here.
Compatibility
editGenerally speaking, the Curator should be able to perform a remote reindex from any version of Elasticsearch, 1.4 and newer. Strictly speaking, the Reindex API in Elasticsearch is able to reindex from older clusters, but Curator cannot be used to facilitate this due to Curator’s dependency on changes released in 1.4.
However, there is a known bug with Elasticsearch 5.3.0 not being able to reindex from remote clusters older than 2.0. The patch is available in Elasticsearch 5.3.1. Earlier versions of Elasticsearch 5.x do not suffer from this bug. This bug appeared again in Elasticsearch 5.4.0, and was fixed in 5.4.1, and hopefully will not appear in any other future releases.