Briefly, this error occurs when Elasticsearch tries to persist cluster state but encounters an issue. This could be due to insufficient disk space, incorrect file permissions, or a network connectivity problem. To resolve this, ensure there’s enough disk space and correct file permissions are set. If it’s a network issue, check the connectivity between nodes. Also, ensure the master node is functioning properly as it’s responsible for persisting cluster state.
This guide will help you check for common problems that cause the log ” asked for state to be persisted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “asked for state to be persisted” classname is JobModelSnapshotUpgrader.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
};
// Execute callback in the UTILITY thread pool; as the current thread in the callback will be one in the
// autodetectWorkerExecutor. Trying to run the callback in that executor will cause a dead lock as that
// executor has a single processing queue.
(aVoid; e) -> threadPool.executor(UTILITY_THREAD_POOL_NAME).execute(() -> shutdown(e)));
logger.info("asked for state to be persisted");
};
f -> {
logger.error(
() -> new ParameterizedMessage(
"[{}] [{}] failed to update snapshot upgrader task to started";
[ratemypost]
