Failed to invoke shard touring changed callback – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is unable to execute a callback function after a shard operation. This could be due to a variety of reasons such as network issues, resource constraints, or a bug in the callback function itself. To resolve this issue, you can try the following: 1) Check the network connectivity and ensure that all nodes are reachable. 2) Monitor the resource usage of your Elasticsearch cluster and scale it up if necessary. 3) Review the callback function for any potential bugs or issues.

This guide will help you check for common problems that cause the log ” [{}] failed to invoke shard touring changed callback ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, shard.

Log Context

Log “[{}] failed to invoke shard touring changed callback” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    public void shardRoutingChanged(IndexShard indexShard; @Nullable ShardRouting oldRouting; ShardRouting newRouting) {
        for (IndexEventListener listener : listeners) {
            try {
                listener.shardRoutingChanged(indexShard; oldRouting; newRouting);
            } catch (Exception e) {
                logger.warn(() -> new ParameterizedMessage("[{}] failed to invoke shard touring changed callback";
                    indexShard.shardId().getId()); e);


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?