Voting-only node skipping local publication to – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.2-8.9

Briefly, this error occurs when a node in Elasticsearch cluster is set as a “voting-only” node. This means it participates in elections for a new master node but doesn’t hold any data or perform any other tasks. The error message indicates that the node is skipping local publication due to its voting-only status. To resolve this, you can either change the node’s role from “voting-only” to a regular node or data node, or you can ignore the message if the node’s role is intentionally set to voting-only and it’s functioning as expected.

This guide will help you check for common problems that cause the log ” voting-only node skipping local publication to ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node, cluster.

Log Context

Log “voting-only node skipping local publication to” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (isVotingOnlyNode) {
 // Voting-only nodes publish their cluster state to other nodes in order to freshen the state held
 // on other full master nodes; but then fail the publication before committing. However there's no
 // need to freshen our local state so we can fail right away.
 throw new TransportException(
 new ElasticsearchException("voting-only node skipping local publication to " + destination)
 } else {
 return handlePublishRequest.apply(publishRequest);


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?