Skip to content

Commit

Permalink
[DOCS] Add deprecation docs for low ILM poll intervals (#77733) (#78095)
Browse files Browse the repository at this point in the history
We deprecated ILM poll intervals of less than 1 second in 7.2 with PR #41096
However, we didn't add a related item to the 7.2 deprecation docs.
This adds the missing item.

Relates to #41095.
  • Loading branch information
jrodewig authored Sep 21, 2021
1 parent 08d7e31 commit aac5777
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions docs/reference/migration/migrate_7_2.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,9 @@ your application to Elasticsearch 7.2.

See also <<release-highlights>> and <<es-release-notes>>.

* <<breaking_72_discovery_changes>>
* <<breaking_72_ilm_deprecations>>

//NOTE: The notable-breaking-changes tagged regions are re-used in the
//Installation and Upgrade Guide

Expand All @@ -27,4 +30,17 @@ unexpectedly ignored the rest. For instance if you set `discovery.seed_hosts:
"10.11.12.13:9300-9310"` then {es} would only use `10.11.12.13:9300` for
discovery. Seed host addresses containing port ranges are now rejected.

[discrete]
[[breaking_72_ilm_deprecations]]
=== {ilm-cap} ({ilm-init}) deprecations

[discrete]
[[deprecate-ilm-poll-interval-1s]]
==== An {ilm-init} poll interval of less than one second is deprecated.

Setting `indices.lifecycle.poll_interval` to less than one second (`1s`) is now
deprecated. If the `indices.lifecycle.poll_interval` cluster setting is too low,
it can cause excessive load on a cluster.

To avoid deprecation warnings, use a setting value of `1s` or greater.
// end::notable-breaking-changes[]

0 comments on commit aac5777

Please sign in to comment.