Briefly, this error occurs when a request to allocate data frame analytics memory is made on a non-master node in Elasticsearch. Elasticsearch requires such operations to be performed on the master node. To resolve this issue, you can either redirect the request to the master node or configure your cluster to allow non-master nodes to handle such requests. However, the latter option may affect the performance and stability of your cluster, so it’s generally recommended to perform these operations on the master node.
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: memory, request, plugin, node.
Log Context
Log “Request to put data frame analytics memory requirement on non-master node” class name 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());
[ratemypost]
