root
/
elasticsearch
mirror of https://github.com/elastic/elasticsearch.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity
elasticsearch/docs/reference/migration/migrate_8_0/breaker.asciidoc

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

20 lines
728 B
Plaintext
Raw Normal View History

[DOCS] Swap `[float]` for `[discrete]` (#60124) Changes instances of `[float]` in our docs for `[discrete]`. Asciidoctor prefers the `[discrete]` tag for floating headings: https://asciidoctor.org/docs/asciidoc-asciidoctor-diffs/#blocks
2020-07-23 23:48:22 +08:00
[discrete]
Fixed synchronizing REST API inflight breaker names with internal variable (#40878) The internal configuration settings were like that: network.breaker.inflight_requests But the exposed REST API had the value names with underscore like that: network.breaker.in_flight_requests This was now corrected to without underscores like that: network.breaker.inflight_requests
2019-09-03 20:56:36 +08:00
[[breaking_80_breaker_changes]]
Rebranded breaking changes as the migration guide (#67496) * Rebranded breaking changes as the migration guide * Fixed heading level
2021-01-15 01:14:48 +08:00
==== Circuit breaker changes
Fixed synchronizing REST API inflight breaker names with internal variable (#40878) The internal configuration settings were like that: network.breaker.inflight_requests But the exposed REST API had the value names with underscore like that: network.breaker.in_flight_requests This was now corrected to without underscores like that: network.breaker.inflight_requests
2019-09-03 20:56:36 +08:00
[DOCS] Fix tags and xrefs for 8.0 breaking changes (#75712) A tag is required to reuse Elasticsearch breaking changes in the Stack Guide. To display properly, the breaking changes must use external links rather than xrefs. This PR correctly places those tags for reuse. It also replaces several xrefs with external links for reuse.
2021-07-27 05:43:39 +08:00
//NOTE: The notable-breaking-changes tagged regions are re-used in the
//Installation and Upgrade Guide
Fixed synchronizing REST API inflight breaker names with internal variable (#40878) The internal configuration settings were like that: network.breaker.inflight_requests But the exposed REST API had the value names with underscore like that: network.breaker.in_flight_requests This was now corrected to without underscores like that: network.breaker.inflight_requests
2019-09-03 20:56:36 +08:00
//tag::notable-breaking-changes[]
[DOCS] Add collapsible sections to 8.0 breaking changes [Part 2] (#55862)
2020-05-05 21:44:29 +08:00
.The `in_flight_requests` stat has been renamed `inflight_requests` in logs and diagnostic APIs.
[%collapsible]
====
*Details* +
Fixed synchronizing REST API inflight breaker names with internal variable (#40878) The internal configuration settings were like that: network.breaker.inflight_requests But the exposed REST API had the value names with underscore like that: network.breaker.in_flight_requests This was now corrected to without underscores like that: network.breaker.inflight_requests
2019-09-03 20:56:36 +08:00
The name of the in flight requests circuit breaker in log output and diagnostic APIs (such as the node stats API) changes from `in_flight_requests` to `inflight_requests` to align it with the name of the corresponding settings.
[DOCS] Add collapsible sections to 8.0 breaking changes [Part 2] (#55862)
2020-05-05 21:44:29 +08:00
*Impact* +
Update your workflow and applications to use the `inflight_requests` stat in
place of `in_flight_requests`.
====
Fixed synchronizing REST API inflight breaker names with internal variable (#40878) The internal configuration settings were like that: network.breaker.inflight_requests But the exposed REST API had the value names with underscore like that: network.breaker.in_flight_requests This was now corrected to without underscores like that: network.breaker.inflight_requests
2019-09-03 20:56:36 +08:00
//end::notable-breaking-changes[]