Removing custom meta data type – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch is trying to remove a custom metadata type that was previously added. This could be due to a change in the index settings or a cleanup process. To resolve this issue, you can either re-add the custom metadata type if it’s still needed, or ensure that no processes are trying to access this metadata after it’s been removed. Also, check your Elasticsearch version, as older versions may have issues with handling custom metadata. Lastly, ensure your index settings are correctly configured to avoid unnecessary removal of metadata.

This guide will help you check for common problems that cause the log ” [{}] removing custom meta data type [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: tribe.

Log Context

Log “[{}] removing custom meta data type [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                if (mergedCustomMetaData == null) {
                    // we ignore merging custom md which doesn't implement MergableCustomMetaData interface
                    if (currentState.metaData().custom(changedCustomMetaDataType) instanceof MergableCustomMetaData) {
                        // custom md has been removed
                        clusterStateChanged = true;
              "[{}] removing custom meta data type [{}]"; tribeName; changedCustomMetaDataType);
                } else {
                    // custom md has been changed
                    clusterStateChanged = true;


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?