Briefly, this error occurs when Elasticsearch is unable to access the JNA (Java Native Access) library, which is used to interact with native system libraries. This could be due to incorrect permissions, missing library, or an incompatible version. To resolve this issue, ensure that the JNA library is correctly installed and the Elasticsearch process has the necessary permissions to access it. Also, check if the version of the JNA library is compatible with your Elasticsearch version. If not, upgrade or downgrade the library as needed.
This guide will help you check for common problems that cause the log ” unable to retrieve max number of threads [” + JNACLibrary.strerror(Native.getLastError()) + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: threads, bootstrap.
Log Context
Log “unable to retrieve max number of threads [” + JNACLibrary.strerror(Native.getLastError()) + “]” classname is JNANatives.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final JNACLibrary.Rlimit rlimit = new JNACLibrary.Rlimit();
if (JNACLibrary.getrlimit(rlimit_nproc; rlimit) == 0) {
MAX_NUMBER_OF_THREADS = rlimit.rlim_cur.longValue();
} else {
logger.warn("unable to retrieve max number of threads [" + JNACLibrary.strerror(Native.getLastError()) + "]");
}
}
}
static void trySetMaxSizeVirtualMemory() {
