How To Solve Issues Related to Log – Cannot mlockall because JNA is not available

Prevent ES settings related problems

Check if your ES issues are caused from misconfigured settings

Resolve Issue

Updated: Jan-20

In Page Navigation (click to jump) :
Troubleshooting Background       
Related Issues  
Log Context
About Opster

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

Troubleshooting background

To troubleshoot Elasticsearch log “Cannot mlockall because JNA is not available” 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 load JNA native support library Elasticsearch 6.x 6 5.82 K 

2 Elasticsearch 2 0 Warning Jna Is No    


Log Context

Log ”Cannot mlockall because JNA is not available” classname is Natives.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

         JNA_AVAILABLE = v;
    }

    static void tryMlockall() {
        if (!JNA_AVAILABLE) {
            logger.warn("cannot mlockall because JNA is not available");
            return;
        }
        JNANatives.tryMlockall();
    }







About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

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

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?