How To Solve Issues Related to Log – Logger.warnmessage; params;

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Jan-20

In Page Navigation (click to jump) :
Troubleshooting Background       
Related Issues  
Log Context
About Opster

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Logger.warnmessage; params;” it’s important to understand common problems related to Elasticsearch concepts: deprecation. See detailed explanations below complete with common problems, examples and useful tips.

Deprecation in Elasticsearch

What it is

Deprecation refers to processes and functions that are in the process of being eliminated and (possibly) replaced by newer ones.

Typically, a function will not disappear from one version to the next without warning. Normally this will happen across a number of versions. When you use a deprecated function in intermediate versions, it will continue to work as before, but you will receive warnings that the function in question is intended to disappear in the future.

How it works

There are a number of ways you can find out which functions have been deprecated, including: deprecation logs, reading the breaking pages documentation and paying attention to warnings.

In a deprecation log:

{"type": "deprecation", "timestamp": "2020-01-16T12:50:11,263+0000", "level": "WARN", "component": "o.e.d.r.a.d.RestDeleteAction", "": "docker-cluster", "": "es01", "cluster.uuid": "VGTYFgunQ_STTKVz6YHAGg", "": "wh5J7TJ-RD-pJE4JOUjVpw",  "message": "[types removal] Specifying types in document index requests is deprecated, use the typeless endpoints instead (/{index}/_doc/{id}, /{index}/_doc, or /{index}/_create/{id})."  }

Reading the breaking changes documentation for each version:

In kibana you may also see a warning if you run a deprecated command in the development panel:

#! Deprecation: [types removal] Specifying types in document index requests is deprecated, use the typeless endpoints instead (/{index}/_doc/{id}, /{index}/_doc, or /{index}/_create/{id}).

It is important to act upon these warnings. Although your application still works, ignoring the warnings will almost certainly cause things to malfunction in a future upgrade.

Deprecation API

There is a depreciation API, which can help point you to deprecated functions on your cluster:

Version 5.6-6.8

GET /_xpack/migration/deprecations

Version 7

GET /_migration/deprecations

However, you should never depend on the deprecation API alone. Just because the API returns with no issues, it does not mean that everything in your setup will work out of the box when migrating!  This is to be used in addition to looking through the deprecation log and breaking changes documentation.

  • The removal of document types (“_type”) . Various document types were allowed in a single index in version 6, but this functionality has been removed. You will get warnings if you use document types in queries, and only 1 document type is allowed per index in version 7.  The functionality is expected to be completely removed in version 8.
  • The discovery.zen.minimum_master_nodes setting is permitted, but ignored, on 7.x nodes.

There are many more examples to be found in the breaking changes documentation.

Notes and good things to know

It is important to visit ALL  the breaking changes for each minor version between the version you are using and the version you want to upgrade to.

Contains information that is not mentioned on the next page.

The best way is to go to the “breaking changes” page of the version you want to upgrade to, and then use the links to page look through all of the minor version pages down to the one you want to upgrade from, paying particular attention to the major version change (eg. 7.0 )

Opster supports all Elasticsearch versions so If you need help reach out

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Logger warning using Elasticsearch Java API 1.18 K 1

2W Do I Disable Log Messages From Th  

Log Context

Log ”Logger.warn(message; params);” classname is
We have extracted the following from Elasticsearch source code to get an in-depth context :


        if (log) {
            logger.warn(message; params);

     * Format a warning string in the proper warning format by prepending a warn code; warn agent; wrapping the warning string in quotes;

About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?