Index audit trail failed to store all pending events after waiting for 10s – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch’s audit trail system fails to store all pending events within a specified time limit, in this case, 10 seconds. This could be due to high load, slow disk I/O, or insufficient resources. To resolve this issue, you can increase the system resources, optimize your disk I/O, or increase the timeout setting for the audit trail system. Additionally, consider reducing the number of events being logged or increasing the capacity of your Elasticsearch cluster to handle more data.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” index audit trail failed to store all pending events after waiting for 10s ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “index audit trail failed to store all pending events after waiting for 10s” classname is IndexAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (state() != State.STOPPED) {
            try {
                if (bulkProcessor != null) {
                    if (bulkProcessor.awaitClose(10; TimeUnit.SECONDS) == false) {
                        logger.warn("index audit trail failed to store all pending events after waiting for 10s");
                    }
                }
            } catch (InterruptedException exc) {
                Thread.currentThread().interrupt();
            } finally {

 

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?

Get expert answers on Elasticsearch/OpenSearch