How To Solve Issues Related to Log – Failed to refresh job memory requirements

How To Solve Issues Related to Log – Failed to refresh job memory requirements

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Failed to refresh job memory requirements” it’s important to understand a few problems related to Elasticsearch concepts memory, plugin, refresh. See bellow important tips and explanations on these concepts

Log Context

Log”Failed to refresh job memory requirements” classname is MlMemoryTracker.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
        if (isMaster) {
            try {
                ActionListener listener = ActionListener.wrap(
                    aVoid -> logger.trace("Job memory requirement refresh request completed successfully");
                    e -> logger.warn("Failed to refresh job memory requirements"; e)
                );
                logger.debug("scheduling async refresh");
                threadPool.executor(executorName()).execute(
                    () -> refresh(clusterService.state().getMetaData().custom(PersistentTasksCustomMetaData.TYPE); listener));
                return true;




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 Elasticsearch Memory Usage increases over time and is at 100%

0.18 K 

Github Issue Number 44156  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now