Skipping unknown custom object with type – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

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 encounters an unknown custom object type during deserialization. This could be due to a missing plugin or a version mismatch between nodes. To resolve this issue, ensure that all nodes in the cluster are running the same version of Elasticsearch and that all necessary plugins are installed. If the error persists, check your data for any inconsistencies or corruption.

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 ” Skipping unknown custom object with type {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, cluster.

Log Context

Log “Skipping unknown custom object with type {}” classname is Metadata.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    } else {
                        try {
                            Custom custom = parser.namedObject(Custom.class; currentFieldName; null);
                            builder.putCustom(custom.getWriteableName(); custom);
                        } catch (NamedObjectNotFoundException ex) {
                            logger.warn("Skipping unknown custom object with type {}"; currentFieldName);
                            parser.skipChildren();
                        }
                    }
                } else if (token.isValue()) {
                    if ("version".equals(currentFieldName)) {

 

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?