This version of the OpenSearch documentation is no longer maintained. For the latest version, see the current documentation. For information about OpenSearch version maintenance, see Release Schedule and Maintenance Policy.
We don’t recommend changing these settings; the defaults should work well for most use cases.
Index State Management (ISM) stores its configuration in the
.opendistro-ism-config index. Don’t modify this index without using the ISM API operations.
All settings are available using the OpenSearch
_cluster/settings operation. None require a restart, and all can be marked
|Specifies whether ISM is enabled or not.
|The interval at which the managed index jobs are run.
|A randomized delay that is added to a job’s base run time to prevent a surge of activity from all indexes at the same time. A value of 0.6 means a delay of 0-60% of a job interval is added to the base interval. For example, if you have a base interval time of 30 minutes, a value of 0.6 means an amount anywhere between 0 to 18 minutes gets added to your job interval. Maximum is 1, which means an additional interval time of 100%. This maximum cannot exceed
plugins.jobscheduler.jitter_limit, which also has a default of 0.6. For example, if
plugins.index_state_management.jitter is set to 0.8, ISM uses
plugins.jobscheduler.jitter_limit of 0.6 instead.
|How often the routine background sweep is run.
|The backoff time between retries for failures in the
ManagedIndexCoordinator (such as when we update managed indexes).
|The count of retries for failures in the
|Specifies whether audit history is enabled or not. The logs from ISM are automatically indexed to a logs document.
|The maximum number of documents before rolling over the audit history index.
|The maximum age before rolling over the audit history index.
|The time between rollover checks for the audit history index.
|How long audit history indexes are kept.
|List of actions that you can use.