Job update was submitted to non-master node – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when an Elasticsearch job update is submitted to a non-master node. In Elasticsearch, certain operations like creating, updating, or deleting indices should be performed on the master node. If these operations are performed on non-master nodes, it can lead to inconsistencies and errors. To resolve this issue, you can ensure that job updates are always submitted to the master node. You can do this by checking the node’s role before submitting a job update. Alternatively, you can configure your client to automatically redirect requests to the master node.

This guide will help you check for common problems that cause the log ” Job update was submitted to non-master node [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node and plugin.

Log Context

Log “Job update was submitted to non-master node [” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         UpdateHolder updateHolder =;
        UpdateParams update = updateHolder.update;

        if (update.isJobUpdate() && clusterService.localNode().isMasterNode() == false) {
            assert clusterService.localNode().isMasterNode();
            logger.error("Job update was submitted to non-master node [" + clusterService.getNodeName() + "]; update for job ["
                    + update.getJobId() + "] will be ignored");


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?