版本： 7.17-8.9
简而言之，当 Elasticsearch 主节点处理过时的分片启动事件时会出现此错误。这可能是由于网络问题、节点故障或处理缓慢导致的。要解决此问题，可以尝试重启 Elasticsearch 集群以刷新分片状态。如果问题持续存在，请检查网络连接问题或硬件故障。此外，如果节点负载过重，考虑增加节点资源，因为这可能导致处理时间缓慢。
日志上下文 #
日志 “master processed stale shard-started event; failing shard” 的类名是 IndexShard.java. 我们从 Elasticsearch 源代码中提取了以下内容，供那些寻求深入上下文的人参考：
//
// NB this can only happen on replicas - if it happened to a primary then we'd move to a new primary term and ignore the
// stale shard-started message.
assert newRouting.primary() == false
: "primary routing is active; but local shard state isn't. routing: " + newRouting + "; local state: " + state;
throw new IllegalIndexShardStateException(shardId; state; "master processed stale shard-started event; failing shard");
} persistMetadata(path; indexSettings; newRouting; currentRouting; logger);
final CountDownLatch shardStateUpdated = new CountDownLatch(1);
