Log Illegal state. got wrong mapping task type – How To Solve Related Issues

Log Illegal state. got wrong mapping task type – How To Solve Related Issues

Opster Team

Feb-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 “Illegal state. got wrong mapping task type” 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: cluster, mapping, metadata, task.

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”illegal state; got wrong mapping task type [{}]” classname is MetaDataMappingService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     dirty = true;
                } catch (Throwable t) {
                    logger.warn("[{}] failed to update-mapping in cluster state; type [{}]"; index; updateTask.type);
            } else {
                logger.warn("illegal state; got wrong mapping task type [{}]"; task);
        return dirty;


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 illegal_argument_exception request contains unrecognized parameter: [mapping] – ElasticSearch Index Creation -views 3.22 K ,score 2

How to update the mapping in Elasticsearch to change the field datatype and change the type of analyzers in string -views   18.39 K,score 12


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now