@@ -20,8 +20,8 @@ There are several thread pools, but the important ones include:
2020 `1000`.
2121
2222[[search-throttled]]`search_throttled`::
23- For count/search/suggest/get operations on `search_throttled indices`.
24- Thread pool type is `fixed_auto_queue_size` with a size of `1`, and initial
23+ For count/search/suggest/get operations on `search_throttled indices`.
24+ Thread pool type is `fixed_auto_queue_size` with a size of `1`, and initial
2525 queue_size of `100`.
2626
2727`get`::
@@ -30,7 +30,7 @@ There are several thread pools, but the important ones include:
3030 queue_size of `1000`.
3131
3232`analyze`::
33- For analyze requests. Thread pool type is `fixed` with a size of `1`, queue
33+ For analyze requests. Thread pool type is `fixed` with a size of `1`, queue
3434 size of `16`.
3535
3636`write`::
@@ -51,8 +51,8 @@ There are several thread pools, but the important ones include:
5151 keep-alive of `5m` and a max of `min(10, (# of available processors)/2)`.
5252
5353`listener`::
54- Mainly for java client executing of action when listener threaded is set to
55- `true`. Thread pool type is `scaling` with a default max of
54+ Mainly for java client executing of action when listener threaded is set to
55+ `true`. Thread pool type is `scaling` with a default max of
5656 `min(10, (# of available processors)/2)`.
5757
5858`fetch_shard_started`::
@@ -125,6 +125,9 @@ thread_pool:
125125
126126experimental[]
127127
128+ deprecated[7.7.0,The experimental `fixed_auto_queue_size` thread pool type is
129+ deprecated and will be removed in 8.0.]
130+
128131The `fixed_auto_queue_size` thread pool holds a fixed size of threads to handle
129132the requests with a bounded queue for pending requests that have no threads to
130133service them. It's similar to the `fixed` threadpool, however, the `queue_size`
@@ -202,13 +205,13 @@ processors: 2
202205There are a few use-cases for explicitly overriding the `processors`
203206setting:
204207
205- . If you are running multiple instances of {es} on the same host but want {es}
206- to size its thread pools as if it only has a fraction of the CPU, you should
207- override the `processors` setting to the desired fraction, for example, if
208+ . If you are running multiple instances of {es} on the same host but want {es}
209+ to size its thread pools as if it only has a fraction of the CPU, you should
210+ override the `processors` setting to the desired fraction, for example, if
208211you're running two instances of {es} on a 16-core machine, set `processors` to 8.
209- Note that this is an expert-level use case and there's a lot more involved
210- than just setting the `processors` setting as there are other considerations
211- like changing the number of garbage collector threads, pinning processes to
212+ Note that this is an expert-level use case and there's a lot more involved
213+ than just setting the `processors` setting as there are other considerations
214+ like changing the number of garbage collector threads, pinning processes to
212215cores, and so on.
213216. Sometimes the number of processors is wrongly detected and in such
214217cases explicitly setting the `processors` setting will workaround such
0 commit comments