Log Failed to index audit event: . internal queue is full; which may be caused by a high indexing rate or – How To Solve Related Issues



Log Failed to index audit event: . internal queue is full; which may be caused by a high indexing rate or – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Failed to index audit event: . internal queue is full; which may be caused by a high indexing rate or” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index, plugin.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log “Failed to index audit event: [{}]. internal queue is full; which may be caused by a high indexing rate or” classname is IndexAuditTrail.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     void enqueue(Message message; String type) {
        State currentState = state();
        if (currentState != State.STOPPING && currentState != State.STOPPED) {
            boolean accepted = queueConsumer.offer(message);
            if (!accepted) {
                logger.warn("failed to index audit event: [{}]. internal queue is full; which may be caused by a high indexing rate or " +
                        "issue with the destination"; type);
            }
        }
    }










Find Configuration Errors

Try The Tool