Aborted by user – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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”classname  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 void warnAboutIndexBackup(Terminal terminal) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content