Start readiness service after http is started#136729
Merged
rjernst merged 3 commits intoelastic:mainfrom Oct 21, 2025
Merged
Conversation
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.
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Collaborator
|
Hi @rjernst, I've created a changelog YAML for you. |
mark-vieira
approved these changes
Oct 21, 2025
This was referenced Oct 21, 2025
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.
Collaborator
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.