Skipping unknown custom object with type – How to solve related issues

Average Read Time

2 Mins

Skipping unknown custom object with type – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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: cluster and metadata.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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)) {




 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content