Aborted by user – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when an Elasticsearch operation is manually stopped by a user before it completes. This could be due to a variety of reasons such as the operation taking too long or the user realizing they initiated the wrong operation. To resolve this issue, ensure that the operation is necessary and correct before initiating it. If the operation is taking too long, consider optimizing your Elasticsearch queries or increasing your cluster resources.

This guide will help you check for common problems that cause the log ” aborted by user ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, index.

Log Context

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

 private static void confirm(String msg; Terminal terminal) {
 String text = terminal.readText("Confirm [y/N] ");
 if (text.equalsIgnoreCase("y") == false) {
 throw new ElasticsearchException("aborted by user");
 }  private static void warnAboutIndexBackup(Terminal terminal) {


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?