Log Ml job configurations migrated: – How To Solve Related Issues

Log Ml job configurations migrated: – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Ml job configurations migrated:” it’s important to understand a few problems related to Elasticsearch concepts plugin. See bellow important tips and explanations on these concepts

Log Context

Log”Ml job configurations migrated: {}” classname is MlConfigMigrator.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
            
Override
            public void clusterStateProcessed(String source; ClusterState oldState; ClusterState newState) {
                if (removedConfigs.get() != null) {
                    if (removedConfigs.get().removedJobIds.isEmpty() == false) {
                        logger.info("ml job configurations migrated: {}"; removedConfigs.get().removedJobIds);
                    }
                    if (removedConfigs.get().removedDatafeedIds.isEmpty() == false) {
                        logger.info("ml datafeed configurations migrated: {}"; removedConfigs.get().removedDatafeedIds);
                    }
                }



Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Github Issue Number 32905  

Moving Ml Jobs And Their Data  

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now