Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.7] [DOCS] Add deprecation docs for low ILM poll intervals (#77733) #78091

Merged
merged 1 commit into from
Sep 21, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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[]