GetFreePhysicalMemorySize is not available – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve the free physical memory size of the system. This could be due to insufficient permissions, unsupported operating system, or a JVM misconfiguration. To resolve this issue, you can try running Elasticsearch with administrative privileges, ensure your operating system is supported, or check your JVM configurations. Additionally, you may need to update your Elasticsearch or JVM to the latest version if they are outdated.

This guide will help you check for common problems that cause the log ” getFreePhysicalMemorySize is not available ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: monitor, memory.

Log Context

Log “getFreePhysicalMemorySize is not available” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     * Returns the amount of free physical memory in bytes.
    public long getFreePhysicalMemorySize() {
        if (getFreePhysicalMemorySize == null) {
            logger.warn("getFreePhysicalMemorySize is not available");
            return 0;
        try {
            final long freeMem = (long) getFreePhysicalMemorySize.invoke(osMxBean);
            if (freeMem 


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?