- Curator Index Management:
- About
- Getting Started
- Command Line
- Configuration
- Actions
- Options
- allocation_type
- extra_settings
- continue_if_exception
- count
- delay
- delete_aliases
- disable_action
- ignore_empty_list
- ignore_unavailable
- include_aliases
- include_global_state
- key
- max_num_segments
- name
- partial
- rename_pattern
- rename_replacement
- repository
- retry_count
- retry_interval
- skip_repo_fs_check
- timeout_override
- value
- wait_for_completion
- Filters
- Filter Elements
- 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?
A newer version is available. For the latest information, see the
current release documentation.
max_num_segments
editmax_num_segments
editThis setting is required when using the forceMerge action or the forcemerged filtertype.
The value for this setting is the cutoff number of segments per shard. Indices which have more than this number of segments per shard will remain in the index list.
There is no default value. This setting must be set by the user or an exception will be raised, and execution will halt.
Was this helpful?
Thank you for your feedback.