Aborted – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.7

Briefly, this error occurs when an Elasticsearch operation is prematurely terminated or interrupted. This could be due to a variety of reasons such as insufficient resources, network issues, or a forced shutdown. To resolve this issue, you can try increasing system resources, checking network connectivity, or ensuring that operations are not forcibly terminated. Additionally, check your Elasticsearch logs for more detailed information about the cause of the abort.

This guide will help you check for common problems that cause the log ” Aborted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, repositories.

Log Context

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

 for (String fileName : fileNames) {
 if (snapshotStatus.isAborted()) {
 logger.debug("[{}] [{}] Aborted on the file [{}]; exiting"; shardId; snapshotId; fileName);
 throw new IndexShardSnapshotFailedException(shardId; "Aborted");
 }  logger.trace("[{}] [{}] Processing [{}]"; shardId; snapshotId; fileName);
 final StoreFileMetaData md = metadataFromStore.get(fileName);
 BlobStoreIndexShardSnapshot.FileInfo existingFileInfo = null;


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?