Failed to invoke shard touring changed callback – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many 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. Take a self-guided product tour to see for yourself (no registration required).

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 and 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);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content