# Why setting \`inflight\_requests.type\` is not supported?

**URL:** <https://discuss.elastic.co/t/why-setting-inflight-requests-type-is-not-supported/291002>\
**Category:** Elasticsearch\
**Created:** [December 6, 2021, 3:50am UTC](https://discuss.elastic.co/t/why-setting-inflight-requests-type-is-not-supported/291002 "2021-12-06T03:50:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ViggoC](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viggoc/32/98345_2.png) [@ViggoC](https://discuss.elastic.co/u/ViggoC)\
**Post date:** [December 6, 2021, 3:50am UTC](https://discuss.elastic.co/t/why-setting-inflight-requests-type-is-not-supported/291002/1 "2021-12-06T03:50:21Z")

</div>

I found out that add `inflight_requests.type` in `elasticsearch.yml` is not supported, but `request.type` is ok.

```auto
uncaught exception in thread [main]
java.lang.IllegalArgumentException: unknown setting [network.breaker.inflight_requests.type] did you mean any of [network.breaker.inflight_requests.limit, network.breaker.inflight_requests.overhead]?

```

Reading the code found that only type setting of filed data and request are registered in ClusterSettings.

```auto
HierarchyCircuitBreakerService.FIELDDATA_CIRCUIT_BREAKER_TYPE_SETTING,
HierarchyCircuitBreakerService.REQUEST_CIRCUIT_BREAKER_TYPE_SETTING,

```

What are the considerations. Or is it just because of negligence?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 6, 2021, 8:56am UTC](https://discuss.elastic.co/t/why-setting-inflight-requests-type-is-not-supported/291002/2 "2021-12-06T08:56:29Z")

</div>

It does look like an oversight to me. However, AFAIK none of the `network.breaker.*.type` settings are [documented](https://www.elastic.co/guide/en/elasticsearch/reference/current/circuit-breaker.html) and I don't think it makes much sense for an end-user to change them.

---

<div class="post-metadata">

**Author:** ![ViggoC](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viggoc/32/98345_2.png) [@ViggoC](https://discuss.elastic.co/u/ViggoC)\
**Post date:** [December 7, 2021, 1:40pm UTC](https://discuss.elastic.co/t/why-setting-inflight-requests-type-is-not-supported/291002/3 "2021-12-07T13:40:26Z")

</div>

In fact, I am just confused that one circuit breaker can be configured and the other cannot be configured. Will there be any problems if I register this setting in ClusterSetting?

And, there are currently some settings in the ES source code without corresponding documentation. eg. `indices.id_field_data.enabled`. So for what purpose were they developed if they are not encouraged to use?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 7, 2021, 2:00pm UTC](https://discuss.elastic.co/t/why-setting-inflight-requests-type-is-not-supported/291002/4 "2021-12-07T14:00:05Z")

</div>

There are quite a few settings that are deliberately undocumented and only intended for internal use, e.g. in tests, or to switch on some internally-controlled behaviour.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 4, 2022, 2:00pm UTC](https://discuss.elastic.co/t/why-setting-inflight-requests-type-is-not-supported/291002/5 "2022-01-04T14:00:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.