Total transform count search returned shard failures – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.2-7.5

Briefly, this error occurs when Elasticsearch encounters issues while executing a transform count search, leading to shard failures. This could be due to insufficient resources, network issues, or corrupted shards. To resolve this, you can try increasing the resources allocated to Elasticsearch, checking your network connectivity, or repairing the corrupted shards. If the issue persists, consider re-indexing your data or splitting your index into smaller, more manageable shards.

This guide will help you check for common problems that cause the log ” total transform count search returned shard failures: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, shard, plugin.

Log Context

Log “total transform count search returned shard failures: {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


        ActionListener totalTransformCountListener = ActionListener.wrap(
            transformCountSuccess -> {
                if (transformCountSuccess.getShardFailures().length > 0) {
                    logger.error("total transform count search returned shard failures: {}";
                long totalTransforms = transformCountSuccess.getHits().getTotalHits().value;
                if (totalTransforms == 0) {
                    listener.onResponse(new TransformFeatureSetUsage(available();


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?