Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
Take a self-guided product tour to see for yourself (no registration required).This guide will help you check for common problems that cause the log ” failed to acquire close-read-lock ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “failed to acquire close-read-lock”classname is TcpTransport.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
ConnectionProfile finalProfile = maybeOverrideConnectionProfile(profile);
if (closeLock.readLock().tryLock() == false) {
ensureOpen();
assert false : "should not get here ever because close-write-lock should only be held on shutdown";
throw new ConnectTransportException(node; "failed to acquire close-read-lock");
}
try {
ensureOpen();
initiateConnection(node; finalProfile; listener);
} finally {
