Failed to refresh job memory requirements – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Failed to refresh job memory requirements ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: memory, plugin and refresh.

Log Context

Log “Failed to refresh job memory requirements” classname is
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");
                    () -> refresh(clusterService.state().getMetaData().custom(PersistentTasksCustomMetaData.TYPE); listener));
                return true;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content