Join target is not initialised yet – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-8.9

Briefly, this error occurs when Elasticsearch tries to execute a join operation before the target index is fully initialized. This could be due to timing issues, where the join operation is executed before the index is ready. To resolve this issue, you can 1) ensure that the target index is fully initialized before executing the join operation, 2) add a delay before the join operation to give the index time to initialize, or 3) use a retry mechanism to execute the join operation again if it fails due to the index not being initialized.

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

Log Context

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

 static class InitialJoinAccumulator implements JoinAccumulator {
 public void handleJoinRequest(DiscoveryNode sender; TransportVersion transportVersion; ActionListener joinListener) {
 assert false : "unexpected join from " + sender + " during initialisation";
 joinListener.onFailure(new CoordinationStateRejectedException("join target is not initialised yet"));
 }  @Override
 public String toString() {
 return "InitialJoinAccumulator";