Expected allocation id with term but found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch tries to allocate a shard to a node but finds a different allocation id or term than expected. This could be due to a network partition, node failure, or manual intervention. To resolve this, you can try to manually reroute the shard using the cluster reroute API, or restart the node. If the issue persists, you may need to restore the data from a snapshot or reindex the data. Always ensure that your cluster state is green before making any changes to avoid data loss.

This guide will help you check for common problems that cause the log ” expected allocation id [{}] with term [{}] but found [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: replication, allocation.

Log Context

Log “expected allocation id [{}] with term [{}] but found [{}]” class name is TransportReplicationAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new ShardNotFoundException(shardId; "expected allocation id [{}] but found [{}]";
 primaryRequest.getTargetAllocationID(); actualAllocationId);
 final long actualTerm = indexShard.getPendingPrimaryTerm();
 if (actualTerm != primaryRequest.getPrimaryTerm()) {
 throw new ShardNotFoundException(shardId; "expected allocation id [{}] with term [{}] but found [{}]";
 primaryRequest.getTargetAllocationID(); primaryRequest.getPrimaryTerm(); actualTerm);
 }  acquirePrimaryOperationPermit(


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?