版本： 6.8-8.9
简而言之，当Elasticsearch尝试将分片迁移到目标节点时，如果源分片尚未标记为正在迁移状态，就会出现此错误。这可能是由于集群状态更新延迟或网络问题导致的。要解决此问题，您可以尝试手动迁移分片，确保集群状态已更新，或检查节点之间的网络连接问题。此外，还要确保目标节点有足够的资源来处理该分片。
日志上下文 #
日志"source shard is not marked yet as relocating to [" + request.targetNode() + “]“的类名是 PeerRecoverySourceService.java。我们从Elasticsearch源代码中提取了以下内容，供那些寻求深入上下文的人参考：
logger.debug(
"delaying recovery of {} as source shard is not marked yet as relocating to {}";
request.shardId();
request.targetNode()
);
throw new DelayRecoveryException("source shard is not marked yet as relocating to [" + request.targetNode() + "]");
} RecoverySourceHandler handler = ongoingRecoveries.addNewRecovery(request; task; shard);
logger.trace(
"[{}][{}] starting recovery to {}";
