- Curator Index Management:
- About
- Versions
- Installation
- Running Curator
- Configuration
- Actions
- Options
- allocation_type
- continue_if_exception
- count
- delay
- delete_aliases
- disable_action
- extra_settings
- ignore_empty_list
- ignore_unavailable
- include_aliases
- include_global_state
- indices
- key
- max_num_segments
- name
- partial
- rename_pattern
- rename_replacement
- repository
- retry_count
- retry_interval
- routing_type
- setting
- skip_repo_fs_check
- timeout_override
- value
- wait_for_completion
- Filters
- Filter Elements
- Examples
- Security
- Frequently Asked Questions
- Q: How can I report an error in the documentation?
- Q: Can I delete only certain data from within indices?
- Q: Can Curator handle index names with strange characters?
- Q: I’m getting
DistributionNotFoundandentry_pointerrors when I try to run Curator. What am I doing wrong? - Q: Snapshots seem to be working. Why am I getting
SnapshotMissingExceptionmessages? - Q: Why doesn’t Curator 4 work with older indices?
- Q: Why doesn’t Curator 4 work with AWS Elasticsearch?
- Q: Why am I getting an error message about ASCII encoding?
A newer version is available. For the latest information, see the
current release documentation.
Features
editFeatures
editCurator allows for many different operations to be performed to both indices and snapshots, including:
- Add or remove indices (or both!) from an alias
- Change shard routing allocation
- Close indices
- Create index
- Delete indices
- Delete snapshots
- Open closed indices
- forceMerge indices
- Change the number of replicas per shard for indices
- Take a snapshot (backup) of indices
- Restore snapshots
Was this helpful?
Thank you for your feedback.