Encountered I O error trying to update file settings timestamp – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.9

Briefly, this error occurs when Elasticsearch is unable to update the timestamp of file settings due to an Input/Output (I/O) error. This could be due to insufficient disk space, file permission issues, or a faulty disk. To resolve this issue, you can try freeing up disk space, checking and correcting file permissions, or replacing the faulty disk. Additionally, ensure that the Elasticsearch process has the necessary permissions to write to the directory where the file settings are stored.

This guide will help you check for common problems that cause the log ” encountered I/O error trying to update file settings timestamp ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: settings.

Log Context

Log “encountered I/O error trying to update file settings timestamp” classname is AbstractFileWatchingService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (watching()) {
            if (shouldRefreshFileState(clusterState) && Files.exists(watchedFile())) {
                try {
                    Files.setLastModifiedTime(watchedFile(); FileTime.from(Instant.now()));
                } catch (IOException e) {
                    logger.warn("encountered I/O error trying to update file settings timestamp"; 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?