Node is shutting down – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.11-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when an Elasticsearch node is in the process of shutting down, either due to a manual shutdown command or because of an internal issue like a system failure or resource exhaustion. To resolve this issue, you can check the system logs to identify any underlying problems. If it’s a manual shutdown, ensure the command was intentional. If it’s due to resource exhaustion, consider increasing system resources or optimizing your Elasticsearch configuration to use resources more efficiently. If it’s a system failure, investigate the cause and apply necessary fixes.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” node is shutting down ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node, recovery, indices.

Log Context

Log “node is shutting down” class name is PeerRecoveryTargetService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 );
 }
 Throwable cause = ExceptionsHelper.unwrapCause(e);
 if (transportService.lifecycleState() != Lifecycle.State.STARTED) {
 // the node is shutting down; we just fail the recovery to release resources
 onGoingRecoveries.failRecovery(recoveryId; new RecoveryFailedException(request; "node is shutting down"; cause); false);
 return;
 }
 if (cause instanceof CancellableThreads.ExecutionCancelledException) {
 // this can also come from the source wrapped in a RemoteTransportException
 onGoingRecoveries.failRecovery(

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?