How To Solve Issues Related to Log – Increase RLIMITMEMLOCK ulimit.

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Prevent Issue

Updated: Jan-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Increase RLIMITMEMLOCK ulimit.” it’s important to understand common problems related to Elasticsearch concepts: bootstrap. See detailed explanations below complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Unable to lock JVM Memory: error=12, reason=Cannot allocate memory – Elasticsearch 6.2.4 5.38 K 5

2Elasticsearch data path on a Vagrant shared directory 0.38 K 


Log Context

Log ”Increase RLIMIT_MEMLOCK (ulimit).” classname is JNANatives.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

                                 user; user; user
                                );
                    logger.warn("If you are logged in interactively; you will have to re-login for the new limits to take effect.");
                }
            } else {
                logger.warn("Increase RLIMIT_MEMLOCK (ulimit).");
            }
        }
    }

    static void trySetMaxNumberOfThreads() {






About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster