Ml job 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) job configurations are migrated from an older version to a newer one. 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 that the new configurations are compatible with the newer version. You can also check the Elasticsearch logs for any related errors or warnings. If problems persist, consider reindexing your data or recreating your ML jobs in the new version.

This guide will help you check for common problems that cause the log ” ml job 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 job configurations migrated: {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            public void clusterStateProcessed(String source; ClusterState oldState; ClusterState newState) {
                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);