Deprecation component started – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.16-8.9

Briefly, this error occurs when you are using a feature or component in Elasticsearch that is marked as deprecated. This means that the feature or component is still functional in the current version, but it will be removed or replaced in future versions. To resolve this issue, you should identify the deprecated component and replace it with the recommended alternative. You can also check the Elasticsearch documentation or release notes for information about deprecated features and their replacements.

This guide will help you check for common problems that cause the log ” deprecation component started ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, deprecation.

Log Context

Log “deprecation component started” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    protected void doStart() {"deprecation component started");
        Loggers.addAppender(LogManager.getLogger("org.elasticsearch.deprecation"); this.appender);