GetTotalPhysicalMemorySize 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 access the total physical memory size of the system. This could be due to insufficient permissions or an unsupported operating system. To resolve this issue, you can try running Elasticsearch with administrator or root privileges. Alternatively, ensure that your operating system is compatible with Elasticsearch. If the problem persists, consider upgrading Elasticsearch to the latest version as it may contain fixes for this issue.

This guide will help you check for common problems that cause the log ” getTotalPhysicalMemorySize 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 “getTotalPhysicalMemorySize is not available” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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


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?