Interrupted by – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.3-7.17

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 operation is interrupted before it can complete. This could be due to a system shutdown, network issues, or a resource constraint like memory or CPU overload. To resolve this, you can try increasing system resources, checking network connectivity, or ensuring that the system is not being shut down during operation. If the error persists, you may need to debug the operation to identify the exact cause of the interruption.

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 ” interrupted by ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery.

Log Context

Log “interrupted by” class name is UnicastZenPing.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return hosts -> SeedHostsResolver.resolveHostsLists(new CancellableThreads() {
 public void execute(Interruptible interruptible) {
 try {
 interruptible.run();
 } catch (InterruptedException e) {
 throw new CancellableThreads.ExecutionCancelledException("interrupted by " + e);
 }
 }
 }; unicastZenPingExecutorService; logger; hosts; transportService; resolveTimeout);
 }

 

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?