anchor.diff:  Adds or removes master-eligible nodes from the
   <<modules-discovery-voting,voting configuration exclusion list>>.
   
  -[float]
  -==== Request
   
  -`POST _cluster/voting_config_exclusions/<node_name>` +
  +[[voting-config-exclusions-api-request]]
  +==== {api-request-title}
  +
  +`POST _cluster/voting_config_exclusions/{node_name}` +
   
   `DELETE _cluster/voting_config_exclusions`
   
  -[float]
  -==== Path parameters
   
  -`node_name`::
  -  A <<cluster-nodes,node filter>> that identifies {es} nodes.
  -
  -[float]
  -==== Description
  +[[voting-config-exclusions-api-desc]]
  +==== {api-description-title}
     
   By default, if there are more than three master-eligible nodes in the cluster
   and you remove fewer than half of the master-eligible nodes in the cluster at
  
positive.code: required when removing master-ineligible nodes or fewer than half of the
  master-eligible nodes.
  
  The <<modules-discovery-settings,`cluster.max_voting_config_exclusions`
  setting>> limits the size of the voting configuration exclusion list. The
  default value is `10`. Since voting configuration exclusions are persistent and
  limited in number, you must clear the voting config exclusions list once the
  exclusions are no longer required.
  
  There is also a
  <<modules-discovery-settings,`cluster.auto_shrink_voting_configuration` setting>>,
  which is set to true by default. If it is set to false, you must use this API to
  maintain the voting configuration.
  
  For more information, see <<modules-discovery-removing-nodes>>.
  
  [float]
  ==== Examples
  
  Add `nodeId1` to the voting configuration exclusions list:
  [source,js]
  -------------------------------------------------- 
  POST /_cluster/voting_config_exclusions/nodeId1
  
negative.code: // CONSOLE
  // TEST[catch:bad_request]
  
  
  Remove all exclusions from the list:
  
  [source,js]
  --------------------------------------------------
  DELETE /_cluster/voting_config_exclusions
  