Added new IM 1.2 settings
Signed-off-by: keithhc2 <keithhc2@users.noreply.github.com>
This commit is contained in:
parent
8332843c5a
commit
66df9f9cd5
|
@ -0,0 +1,22 @@
|
|||
---
|
||||
layout: default
|
||||
title: Settings
|
||||
parent: Index rollups
|
||||
nav_order: 30
|
||||
---
|
||||
|
||||
# Index rollup settings
|
||||
|
||||
We don't recommend changing these settings; the defaults should work well for most use cases.
|
||||
|
||||
All settings are available using the OpenSearch `_cluster/settings` operation. None require a restart, and all can be marked `persistent` or `transient`.
|
||||
|
||||
Setting | Default | Description
|
||||
:--- | :--- | :---
|
||||
`plugins.rollup.search.backoff_millis` | 1000 milliseconds | The backoff time between retries for failed rollup jobs.
|
||||
`plugins.rollup.search.backoff_count` | 5 | How many retries the plugin should attempt for failed rollup jobs.
|
||||
`plugins.rollup.search.search_all_jobs` | false | Whether OpenSearch should return all jobs that match the specified search term. If disabled, OpenSearch returns just one of the jobs that matches the term, as opposed to all.
|
||||
`plugins.rollup.dashboards.enabled` | true | Whether rollups are enabled in OpenSearch Dashboards.
|
||||
`plugins.rollup.enabled` | true | Whether the rollup plugin is enabled.
|
||||
`plugins.ingest.backoff_millis` | 1000 milliseconds | The backoff time between data ingestions for rollup jobs.
|
||||
`plugins.ingest.backoff_count` | 5 | How many retries the plugin should attempt for failed ingestions.
|
|
@ -17,6 +17,7 @@ Setting | Default | Description
|
|||
:--- | :--- | :---
|
||||
`plugins.index_state_management.enabled` | True | Specifies whether ISM is enabled or not.
|
||||
`plugins.index_state_management.job_interval` | 5 minutes | The interval at which the managed index jobs are run.
|
||||
`plugins.index_state_management.jitter` | 0.6 | A delay that is added to a job's base run time to prevent a surge of activity from all indices at the same time. A value of 0.6 means 60% of run time is added to the base run time. For example, if you have a base run time of 30 minutes, a value of 0.6 means 18 minutes gets added to your run time, for a total of 48 minutes. Maximum is 1, which means an additional run 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.
|
||||
`plugins.index_state_management.coordinator.sweep_period` | 10 minutes | How often the routine background sweep is run.
|
||||
`plugins.index_state_management.coordinator.backoff_millis` | 50 milliseconds | The backoff time between retries for failures in the `ManagedIndexCoordinator` (such as when we update managed indices).
|
||||
`plugins.index_state_management.coordinator.backoff_count` | 2 | The count of retries for failures in the `ManagedIndexCoordinator`.
|
||||
|
|
Loading…
Reference in New Issue