From b0e5fb78235a109b713e4ece7e541fe1b98e54ee Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Tue, 4 Nov 2014 14:27:22 +0100 Subject: [PATCH] Update zen.asciidoc Tidied up the "No master block" asciidoc --- docs/reference/modules/discovery/zen.asciidoc | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/reference/modules/discovery/zen.asciidoc b/docs/reference/modules/discovery/zen.asciidoc index 2f2d0ab9f72..33c5c261000 100644 --- a/docs/reference/modules/discovery/zen.asciidoc +++ b/docs/reference/modules/discovery/zen.asciidoc @@ -179,10 +179,12 @@ For a node to be fully operational, it must have an active master. The `discover what operations should be rejected when there is no active master. The `discovery.zen.no_master_block` setting has two valid options: -* `all` - All operations on the node. I.e., both read & writes will be rejected. This also applies for api cluster state -read or write operations, like the get index settings, put mapping and cluster state api. -* `write` - Write operations will be rejected. Read operations will succeed, based on the last known cluster configuration. -This may result in partial reads or stale data as this node may be isolated from the rest of the cluster. This is the default. -The `discovery.zen.no_master_block` setting doesn't apply for nodes based apis (for example cluster stats, node info and -node stats apis) which will not be blocked and try to execute on any node possible. \ No newline at end of file +[horizontal] +`all`:: All operations on the node--i.e. both read & writes--will be rejected. This also applies for api cluster state +read or write operations, like the get index settings, put mapping and cluster state api. +`write`:: (default) Write operations will be rejected. Read operations will succeed, based on the last known cluster configuration. +This may result in partial reads of stale data as this node may be isolated from the rest of the cluster. + +The `discovery.zen.no_master_block` setting doesn't apply to nodes based apis (for example cluster stats, node info and +node stats apis) which will not be blocked and try to execute on any node possible.