- 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.
Command-Line Interface (CLI)
editCommand-Line Interface (CLI)
editCurator has always been a command-line tool. When Curator 2.0 was released, it was the first attempt to separate the API from the CLI.
This site provides the documentation for how to use Curator on the command-line.
Learn more about the command-line interface.
Was this helpful?
Thank you for your feedback.