- Curator Index Management:
- Curator and Index Lifecycle Management
- About
- Versions
- Installation
- Running Curator
- Configuration
- Actions
- Options
- allocation_type
- allow_ilm_indices
- continue_if_exception
- copy_aliases
- count
- delay
- delete_after
- delete_aliases
- skip_flush
- disable_action
- extra_settings
- ignore_empty_list
- ignore_unavailable
- include_aliases
- include_global_state
- indices
- key
- max_age
- max_docs
- max_size
- max_num_segments
- max_wait
- migration_prefix
- migration_suffix
- name
- new_index
- node_filters
- number_of_replicas
- number_of_shards
- partial
- post_allocation
- preserve_existing
- refresh
- remote_certificate
- remote_client_cert
- remote_client_key
- remote_filters
- remote_url_prefix
- rename_pattern
- rename_replacement
- repository
- requests_per_second
- request_body
- retry_count
- retry_interval
- routing_type
- search_pattern
- setting
- shrink_node
- shrink_prefix
- shrink_suffix
- slices
- skip_repo_fs_check
- timeout
- timeout_override
- value
- wait_for_active_shards
- wait_for_completion
- wait_for_rebalance
- wait_interval
- warn_if_no_indices
- Filters
- Filter Elements
- aliases
- allocation_type
- count
- date_from
- date_from_format
- date_to
- date_to_format
- direction
- disk_space
- epoch
- exclude
- field
- intersect
- key
- kind
- max_num_segments
- pattern
- period_type
- range_from
- range_to
- reverse
- source
- state
- stats_result
- timestring
- threshold_behavior
- unit
- unit_count
- unit_count_pattern
- use_age
- value
- week_starts_on
- Examples
- Frequently Asked Questions
Cluster Routing
editCluster Routing
editaction: cluster_routing description: "Apply routing rules to the entire cluster" options: routing_type: value: ... setting: enable
Empty values and commented lines will result in the default value, if any, being selected. If a setting is set, but not used by a given action, it will be ignored.
This action changes the shard routing allocation for the selected indices.
See http://www.elastic.co/guide/en/elasticsearch/reference/8.15/shards-allocation.html for more information.
You can optionally set wait_for_completion
to True
to have Curator wait for the shard routing to complete before continuing:
action: cluster_routing description: "Apply routing rules to the entire cluster" options: routing_type: value: ... setting: enable wait_for_completion: True max_wait: 300 wait_interval: 10
This configuration will wait for a maximum of 300 seconds for shard routing and
reallocation to complete before giving up. A max_wait
value of -1
will wait
indefinitely. Curator will poll for completion at 10
second intervals, as
defined by wait_interval
.
Required settings
edit- routing_type
- value
-
setting Currently must be set to
enable
. This setting is a placeholder for potential future expansion.
Optional settings
editSee an example of this action in an actionfile here.
On this page
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now