Skip to content

Conversation

@pugnascotia
Copy link
Contributor

Closes #61767.

When Elasticsearch fails to start up, it tries to print a message to
suggest to the user that they consult the log for more information.
However, if a fatal error is encounted, Elasticsearch exits directly and
no such message is printed.

Improve this situation by printing the same message when Elasticsearch
is about to exit due to a fatal unexpected error.

When Elasticsearch fails to start up, it tries to print a message to
suggest to the user that they consult the log for more information.
However, if a fatal error is encounted, Elasticsearch exits directly and
no such message is printed.

Improve this situation by printing the same message when Elasticsearch
is about to exit due to a fatal unexpected error.
@pugnascotia pugnascotia added >enhancement :Core/Infra/Resiliency Keep running when everything is ok. Die quickly if things go horribly wrong. v8.0.0 v7.15.0 labels Jul 16, 2021
@elasticmachine elasticmachine added the Team:Core/Infra Meta label for core/infra team label Jul 16, 2021
@elasticmachine
Copy link
Collaborator

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

Copy link
Contributor

@stu-elastic stu-elastic left a comment

Choose a reason for hiding this comment

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

Nice.

@pugnascotia pugnascotia merged commit 08ecf23 into elastic:master Jul 21, 2021
@pugnascotia pugnascotia deleted the 61767-logs-suggestion-on-fatal-error branch July 21, 2021 15:47
pugnascotia added a commit that referenced this pull request Jul 21, 2021
Closes #61767.

When Elasticsearch fails to start up, it tries to print a message to
suggest to the user that they consult the log for more information.
However, if a fatal error is encountered, Elasticsearch exits directly and
no such message is printed.

Improve this situation by printing the same message when Elasticsearch
is about to exit due to a fatal unexpected error.
@pugnascotia
Copy link
Contributor Author

Backported to 7.x in dc9ac26.

ywangd pushed a commit to ywangd/elasticsearch that referenced this pull request Jul 30, 2021
Closes elastic#61767.

When Elasticsearch fails to start up, it tries to print a message to
suggest to the user that they consult the log for more information.
However, if a fatal error is encountered, Elasticsearch exits directly and
no such message is printed.

Improve this situation by printing the same message when Elasticsearch
is about to exit due to a fatal unexpected error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Core/Infra/Resiliency Keep running when everything is ok. Die quickly if things go horribly wrong. >enhancement Team:Core/Infra Meta label for core/infra team v7.15.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provide a hint to check the logs if the service does not start

4 participants