Ml datafeed configurations migrated – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.17

Briefly, this error occurs when Elasticsearch Machine Learning (ML) datafeed configurations are updated or moved to a newer version. This is not necessarily an error, but more of an informational message indicating that the migration process has been completed. If you’re experiencing issues, ensure that the migration was successful and no data was lost. Check the compatibility of your applications with the new ML datafeed configurations. If problems persist, consider rolling back to the previous version or seeking assistance from Elasticsearch support.

This guide will help you check for common problems that cause the log ” ml datafeed configurations migrated: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “ml datafeed configurations migrated: {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                if (removedConfigs.get() != null) {
                    if (removedConfigs.get().removedJobIds.isEmpty() == false) {
              "ml job configurations migrated: {}"; removedConfigs.get().removedJobIds);
                    if (removedConfigs.get().removedDatafeedIds.isEmpty() == false) {
              "ml datafeed configurations migrated: {}"; removedConfigs.get().removedDatafeedIds);


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?