Skip to content

Align enrich node settings with the reference page#7066

Open
charlotte-hoblik wants to merge 1 commit into
mainfrom
charlotte-enrich-settings-4370
Open

Align enrich node settings with the reference page#7066
charlotte-hoblik wants to merge 1 commit into
mainfrom
charlotte-enrich-settings-4370

Conversation

@charlotte-hoblik

Copy link
Copy Markdown
Contributor

Aligns the Node settings section of Set up an enrich processor with the enrich settings reference page, following elastic/elasticsearch#150451.

  • enrich.cache_size: match the reference page wording — the three sizing units are now a list, the approximate-size note is split into shorter sentences, and the default moves to the end of the entry. Also fixes an "is is" typo.
  • Add enrich.coordinator_proxy.queue_capacity, which was missing from this page.
  • enrich.max_concurrent_policy_executions: "execute" → "run" to follow the style guide.

Closes #4370.

@charlotte-hoblik charlotte-hoblik self-assigned this Jun 22, 2026
@charlotte-hoblik charlotte-hoblik requested a review from a team as a code owner June 22, 2026 15:18
@charlotte-hoblik charlotte-hoblik added documentation Improvements or additions to documentation docs labels Jun 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@bmorelli25 bmorelli25 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably be reviewed by someone on @elastic/developer-docs as it's not my teams area of expertise. A couple of comments nonetheless:

: Maximum number of searches to include in a [multi-search request]({{es-apis}}operation/operation-msearch) when enriching documents. Defaults to `128`.

`enrich.coordinator_proxy.queue_capacity`
: Coordinator queue capacity. Defaults to `max_concurrent_requests * max_lookups_per_request`.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This defines the setting, but we're not really telling the user what it controls or how/when to tune it. Is there anything more we can offer here to help the reader?

The enrich policy executor is a component that manages the executions of all enrich policies. When an enrich policy is executed, this component creates a new enrich index and removes the previous enrich index. The enrich policy executions are managed from the elected master node. The execution of these policies occurs on a different node.


## Node Settings [ingest-enrich-settings]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A pre-existing problem, but this page's applicability is set to serverless and stack. IIUC, these are elasticsearch.yml settings? Are these supported on serverless? Should we add an applies_to badge to this section?

@bmorelli25 bmorelli25 requested a review from a team June 24, 2026 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Website]: Enrich Settings Docs don't align

2 participants