honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Passthrough special characters in thread pool docs (#55080) 

Some of these characters are special to Asciidoctor and they ruin the
rendering on this page. Instead, we use a macro to passthrough these
characters without Asciidoctor applying any subtitutions to them. This
commit then addresses some rendering issues in the thread pool docs.

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
This commit is contained in:
Jason Tedor 2020-04-10 15:09:27 -04:00
parent 5d4ddf9146
commit d1137ebdaa
No known key found for this signature in database
GPG Key ID: FA89F05560F16BC5
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/reference/modules/threadpool.asciidoc
View File

@ -16,7 +16,7 @@ There are several thread pools, but the important ones include:
`search`::
For count/search/suggest operations. Thread pool type is
`fixed_auto_queue_size` with a size of `int((`<<node.processors,
`# of available_processors`>>` * 3) / 2) + 1`, and initial queue_size of
`# of available_processors`>>`pass:[ * ]3) / 2) + 1`, and initial queue_size of
`1000`.
[[search-throttled]]`search_throttled`::
@ -36,38 +36,38 @@ There are several thread pools, but the important ones include:
`write`::
For single-document index/delete/update and bulk requests. Thread pool type
is `fixed` with a size of <<node.processors, `# of allocated processors`>>,
queue_size of `200`. The maximum size for this pool is `1 + `
<<node.processors, `# of allocated processors`>>.
queue_size of `200`. The maximum size for this pool is
`pass:[1 + ]`<<node.processors, `# of allocated processors`>>.
`snapshot`::
For snapshot/restore operations. Thread pool type is `scaling` with a
keep-alive of `5m` and a max of `min(5, (`<<node.processors,
`# of allocated processors`>>`)/2)`.
`# of allocated processors`>>`) / 2)`.
`warmer`::
For segment warm-up operations. Thread pool type is `scaling` with a
keep-alive of `5m` and a max of `min(5, (`<<node.processors,
`# of allocated processors`>>`)/2)`.
`# of allocated processors`>>`) / 2)`.
`refresh`::
For refresh operations. Thread pool type is `scaling` with a
keep-alive of `5m` and a max of `min(10, (`<<node.processors,
`# of allocated processors`>>`)/2)`.
`# of allocated processors`>>`) / 2)`.
`listener`::
Mainly for java client executing of action when listener threaded is set to
`true`. Thread pool type is `scaling` with a default max of
`min(10, (`<<node.processors, `# of allocated processors`>>`)/2)`.
`min(10, (`<<node.processors, `# of allocated processors`>>`) / 2)`.
`fetch_shard_started`::
For listing shard states.
Thread pool type is `scaling` with keep-alive of `5m` and a default maximum
size of `2 * `<<node.processors, `# of allocated processors`>>.
size of `pass:[2 * ]`<<node.processors, `# of allocated processors`>>.
`fetch_shard_store`::
For listing shard stores.
Thread pool type is `scaling` with keep-alive of `5m` and a default maximum
size of `2 * `<<node.processors, `# of allocated processors`>>.
size of `pass:[2 * ]`<<node.processors, `# of allocated processors`>>.
`flush`::
For <<indices-flush,flush>>, <<indices-synced-flush-api,synced flush>>, and