Skip to content

Start readiness service after http is started#136729

Merged
rjernst merged 3 commits intoelastic:mainfrom
rjernst:readiness/after_http
Oct 21, 2025
Merged

Start readiness service after http is started#136729
rjernst merged 3 commits intoelastic:mainfrom
rjernst:readiness/after_http

Conversation

@rjernst
Copy link
Member

@rjernst rjernst commented Oct 16, 2025

The readiness service indicates when ES is ready to receive external http requests. Yet the service does not actually check http has been started. This commit moves the starting the readiness service to after http has been started. Note that adding a direct dependency between ReadinessService and HttpServerTransport would be complicated, so the "dependency" is achieved by starting readiness almost at the end of node startup.

The readiness service indicates when ES is ready to receive
external http requests. Yet the service does not actually check http has
been started. This commit moves the starting the readiness service to
after http has been started. Note that adding a direct dependency
between ReadinessService and HttpServerTransport would be complicated,
so the "dependency" is achieved by starting readiness almost at the end
of node startup.
@rjernst rjernst requested a review from a team as a code owner October 16, 2025 22:41
@rjernst rjernst added >bug :Core/Infra/Node Lifecycle Node startup, bootstrapping, and shutdown auto-backport Automatically create backport pull requests when merged v8.19.6 v9.1.6 v9.2.1 labels Oct 16, 2025
@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team v9.3.0 labels Oct 16, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine
Copy link
Collaborator

Hi @rjernst, I've created a changelog YAML for you.

@rjernst rjernst merged commit 997e92c into elastic:main Oct 21, 2025
34 checks passed
@rjernst rjernst deleted the readiness/after_http branch October 21, 2025 22:57
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Oct 21, 2025
The readiness service indicates when ES is ready to receive
external http requests. Yet the service does not actually check http has
been started. This commit moves the starting the readiness service to
after http has been started. Note that adding a direct dependency
between ReadinessService and HttpServerTransport would be complicated,
so the "dependency" is achieved by starting readiness almost at the end
of node startup.
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.19
9.1
9.2
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Oct 21, 2025
The readiness service indicates when ES is ready to receive
external http requests. Yet the service does not actually check http has
been started. This commit moves the starting the readiness service to
after http has been started. Note that adding a direct dependency
between ReadinessService and HttpServerTransport would be complicated,
so the "dependency" is achieved by starting readiness almost at the end
of node startup.
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Oct 21, 2025
The readiness service indicates when ES is ready to receive
external http requests. Yet the service does not actually check http has
been started. This commit moves the starting the readiness service to
after http has been started. Note that adding a direct dependency
between ReadinessService and HttpServerTransport would be complicated,
so the "dependency" is achieved by starting readiness almost at the end
of node startup.
elasticsearchmachine pushed a commit that referenced this pull request Oct 21, 2025
The readiness service indicates when ES is ready to receive
external http requests. Yet the service does not actually check http has
been started. This commit moves the starting the readiness service to
after http has been started. Note that adding a direct dependency
between ReadinessService and HttpServerTransport would be complicated,
so the "dependency" is achieved by starting readiness almost at the end
of node startup.
elasticsearchmachine pushed a commit that referenced this pull request Oct 22, 2025
The readiness service indicates when ES is ready to receive
external http requests. Yet the service does not actually check http has
been started. This commit moves the starting the readiness service to
after http has been started. Note that adding a direct dependency
between ReadinessService and HttpServerTransport would be complicated,
so the "dependency" is achieved by starting readiness almost at the end
of node startup.
elasticsearchmachine pushed a commit that referenced this pull request Oct 22, 2025
The readiness service indicates when ES is ready to receive
external http requests. Yet the service does not actually check http has
been started. This commit moves the starting the readiness service to
after http has been started. Note that adding a direct dependency
between ReadinessService and HttpServerTransport would be complicated,
so the "dependency" is achieved by starting readiness almost at the end
of node startup.
fzowl pushed a commit to voyage-ai/elasticsearch that referenced this pull request Nov 3, 2025
The readiness service indicates when ES is ready to receive
external http requests. Yet the service does not actually check http has
been started. This commit moves the starting the readiness service to
after http has been started. Note that adding a direct dependency
between ReadinessService and HttpServerTransport would be complicated,
so the "dependency" is achieved by starting readiness almost at the end
of node startup.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >bug :Core/Infra/Node Lifecycle Node startup, bootstrapping, and shutdown Team:Core/Infra Meta label for core/infra team v8.19.6 v9.1.6 v9.2.1 v9.3.0

3 participants