Desired balance is not computed yet – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.6-8.9

Briefly, this error occurs when Elasticsearch is unable to calculate the desired balance for shard allocation in the cluster. This could be due to a recent cluster state change, or the cluster is still initializing. To resolve this issue, you can try the following: 1) Wait for a few moments and retry the operation, as the balance computation might be in progress. 2) Check the cluster health and ensure all nodes are functioning properly. 3) Review your shard allocation settings, as incorrect configurations could cause this error.

This guide will help you check for common problems that cause the log ” Desired balance is not computed yet ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, allocation, cluster.

Log Context

Log “Desired balance is not computed yet” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  DesiredBalance latestDesiredBalance = desiredBalanceShardsAllocator.getDesiredBalance();
 if (latestDesiredBalance == null) {
 listener.onFailure(new ResourceNotFoundException("Desired balance is not computed yet"));
 var clusterInfo = clusterInfoService.getClusterInfo();
 new DesiredBalanceResponse(


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?