Exception retrieving free physical memory – 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 ” Exception retrieving free physical memory ” 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 “Exception retrieving free physical memory” classname is OsProbe.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 logger.warn("OS reported a negative free memory value [{}]"; freeMem);
                return 0;
            }
            return freeMem;
        } catch (Exception e) {
            logger.warn("exception retrieving free physical memory"; e);
            return 0;
        }
    }

    /**




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content