Briefly, this error occurs when a request to retrieve job memory is made from a non-master node in Elasticsearch. This could be due to misconfiguration or network issues causing the wrong node to be identified as the master. To resolve this, you can try the following: 1) Check your cluster health and ensure the master node is correctly identified. 2) Review your Elasticsearch configuration to ensure nodes are correctly set up. 3) If it’s a network issue, check your network settings and connectivity. 4) Restart the Elasticsearch cluster if necessary.
This guide will help you check for common problems that cause the log ” Request to get job memory not on master node; taskName [{}]; id [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task, master, memory, request.
Overview
A task is an Elasticsearch operation, which can be any request performed on an Elasticsearch cluster, such as a delete by query request, a search request and so on. Elasticsearch provides a dedicated Task API for the task management which includes various actions, from retrieving the status of current running tasks to canceling any long running task.
Examples
Get all currently running tasks on all nodes of the cluster
Apart from other information, the response of the below request contains task IDs of all the tasks which can be used to get detailed information about the particular task in question.
GET _tasks
Get detailed information of a particular task
Where clQFAL_VRrmnlRyPsu_p8A:1132678759 is the ID of the task in below request
GET _tasks/clQFAL_VRrmnlRyPsu_p8A:1132678759
Get all the current tasks running on particular nodes
GET _tasks?nodes=nodeId1,nodeId2
Cancel a task
Where clQFAL_VRrmnlRyPsu_p8A:1132678759 is the ID of the task in the below request
POST /_tasks/clQFAL_VRrmnlRyPsu_p8A:1132678759/_cancel?pretty
Notes
- The Task API will be most useful when you want to investigate the spike of resource utilization in the cluster or want to cancel an operation.
Log Context
Log “Request to get job memory not on master node; taskName [{}]; id [{}]” classname is MlMemoryTracker.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
* or null if it cannot be found.
*/
public Long getJobMemoryRequirement(String taskName; String id) {
if (isMaster == false) {
logger.warn("Request to get job memory not on master node; taskName [{}]; id [{}]"; taskName; id);
return null;
}
// Assume snapshot upgrade tasks have the same memory requirement as the job they correspond to.
if (MlTasks.JOB_SNAPSHOT_UPGRADE_TASK_NAME.equals(taskName)) {
[ratemypost]
