Unable to retrieve resource limits: – 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 ” Unable to retrieve resource limits: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap.

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 “Unable to retrieve resource limits: {}” classname is JNANatives.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 if (JNACLibrary.getrlimit(JNACLibrary.RLIMIT_MEMLOCK; rlimit) == 0) {
                    rlimitSuccess = true;
                    softLimit = rlimit.rlim_cur.longValue();
                    hardLimit = rlimit.rlim_max.longValue();
                } else {
                    logger.warn("Unable to retrieve resource limits: {}"; JNACLibrary.strerror(Native.getLastError()));
        } catch (UnsatisfiedLinkError e) {
            // this will have already been logged by CLibrary; no need to repeat it


Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content