Failed to put mappings on indices – How to solve related issues

Failed to put mappings on indices – How to solve related issues

Opster Team

Feb-21, Version: 1.7-8.0

To understand why Elasticsearch failed to apply mappings, you should run our Elasticsearch Error Check-Up. It’ll check all of your settings and help you resolve issues that lead that to this log and others.

This guide will help you check for common problems that cause the log “Failed to put mappings on indices” to appear. It’s important to understand the issues related to it, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index.

Log Context

Log “[{}] failed to apply mappings” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         final Map updatedEntries;
        try {
            // only update entries if needed
            updatedEntries = internalMerge(newIndexMetaData; MergeReason.MAPPING_RECOVERY; true; true);
        } catch (Exception e) {
            logger.warn(() -> new ParameterizedMessage("[{}] failed to apply mappings"; index()); e);
            throw e;

        boolean requireRefresh = false;


Run the Check-Up to get customized recommendations like this:


The high disk watermark threshold is about to be reached in specific nodes



There are various “watermark” thresholds on each Elasticsearch cluster. When the high disk watermark threshold has been exceeded, it means disk space is running out. The node will…



Based on your specific ES deployment you should…


X-PUT curl -H [a customized code snippet to resolve the issue]

Optimize Elasticsearch Performance

Run The Tool