JNA not found FileSystemNatives methods will be disabled – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.16-8.9

Briefly, this error occurs when Elasticsearch cannot find the Java Native Access (JNA) library, which is used for direct access to native system libraries. This can disable some file system operations. To resolve this issue, ensure that the JNA library is correctly installed and the classpath is properly set. Alternatively, you can download the JNA jar file and place it in the Elasticsearch lib directory. Also, check the Elasticsearch logs for any additional information about the error.

This guide will help you check for common problems that cause the log ” JNA not found. FileSystemNatives methods will be disabled. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “JNA not found. FileSystemNatives methods will be disabled.” classname is FileSystemNatives.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                return WindowsFileSystemNatives.getInstance();
            } else if (Constants.LINUX && Constants.JRE_IS_64BIT) {
                return LinuxFileSystemNatives.getInstance();
        } catch (ClassNotFoundException e) {
            logger.warn("JNA not found. FileSystemNatives methods will be disabled."; e);
        } catch (LinkageError e) {
            logger.warn("unable to load JNA native support library; FileSystemNatives methods will be disabled."; e);


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?