no-master-block.asciidoc 992 B

12345678910111213141516171819202122
  1. [[no-master-block]]
  2. === No master block settings
  3. For the cluster to be fully operational, it must have an active master. The
  4. `discovery.zen.no_master_block` settings controls what operations should be
  5. rejected when there is no active master.
  6. The `discovery.zen.no_master_block` setting has two valid values:
  7. [horizontal]
  8. `all`:: All operations on the node--i.e. both read & writes--will be rejected.
  9. This also applies for api cluster state read or write operations, like the get
  10. index settings, put mapping and cluster state api.
  11. `write`:: (default) Write operations will be rejected. Read operations will
  12. succeed, based on the last known cluster configuration. This may result in
  13. partial reads of stale data as this node may be isolated from the rest of the
  14. cluster.
  15. The `discovery.zen.no_master_block` setting doesn't apply to nodes-based APIs
  16. (for example cluster stats, node info, and node stats APIs). Requests to these
  17. APIs will not be blocked and can run on any available node.