Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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.
This guide will help you check for common problems that cause the log ” Request to put data frame analytics memory requirement on non-master node ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request, plugin, memory, node.
Log Context
Log “Request to put data frame analytics memory requirement on non-master node”classname is MlMemoryTracker.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
* @param listener Called when the refresh is complete or fails. */ public void addDataFrameAnalyticsJobMemoryAndRefreshAllOthers(String id; long mem; ActionListenerlistener) { if (isMaster == false) { listener.onFailure(new NotMasterException("Request to put data frame analytics memory requirement on non-master node")); return; } memoryRequirementByDataFrameAnalyticsJob.put(id; mem + DataFrameAnalyticsConfig.PROCESS_MEMORY_OVERHEAD.getBytes());
See how you can use AutoOps to resolve issues
