Skip to content

[8.18] [docs] ES tutorial on index initialization (#224628)#228334

Merged
kibanamachine merged 1 commit intoelastic:8.18from
kibanamachine:backport/8.18/pr-224628
Jul 16, 2025
Merged

[8.18] [docs] ES tutorial on index initialization (#224628)#228334
kibanamachine merged 1 commit intoelastic:8.18from
kibanamachine:backport/8.18/pr-224628

Conversation

@kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.18:

Questions ?

Please refer to the Backport tool documentation

## Summary

We're seeing a lot of plugins try to use their indices before being
properly initialized leading to search_phase_execution_exceptions since
shards aren't immediately available. This guide aims to give guidance on
how to create indices and be sure they're ready for indexing/searching
in a distributed environment like Kibana.

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

---------

Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
(cherry picked from commit e175389)
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Jul 16, 2025
@kibanamachine kibanamachine enabled auto-merge (squash) July 16, 2025 21:36
@kibanamachine kibanamachine merged commit 3a1a56b into elastic:8.18 Jul 16, 2025
10 of 11 checks passed
@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #71 / ObservabilityApp feature controls observability security feature controls "before all" hook in "observability security feature controls"

Metrics [docs]

✅ unchanged

cc @rudolf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants