GetFreePhysicalMemorySize is not available – How to solve related issues

Average Read Time

2 Mins

GetFreePhysicalMemorySize is not available – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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: memory and monitor.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “GetFreePhysicalMemorySize is not available” classname is OsProbe.java.
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 

 

Run the Check-Up to get customized insights on your system:

Analyze your cluster