From 9d84a856a2fb10691f1e70bc3acb60104b0d8eaf Mon Sep 17 00:00:00 2001 From: Albert Chu Date: Thu, 8 Feb 2018 10:58:20 -0800 Subject: [PATCH] doc/flux-kvs: Remove excessive details --- doc/man1/flux-kvs.adoc | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/doc/man1/flux-kvs.adoc b/doc/man1/flux-kvs.adoc index 2b2c08859d62..78ce8fc573dd 100644 --- a/doc/man1/flux-kvs.adoc +++ b/doc/man1/flux-kvs.adoc @@ -41,14 +41,7 @@ Different KVS namespaces can be created in which kvs values can be read from/written to. By default, all KVS operations operate on the default KVS namespace "primary". An alternate namespace can be specified via the '--namespace' option or the environment variable -FLUX_KVS_NAMESPACE. When a KVS namespace is first created, it is only -created on the leader. Followers will initialize itself against a -namespace the first time it is used. When a namespace is removed, a -namespace is marked for removal on the leader and an event is -multicast to followers to similarly mark the namespace for removal. -The namespace will then be garbage collected in the background. There -may be a delay in the namespace being recognized as removed. Similar -to commits, it is "eventually consistent". +FLUX_KVS_NAMESPACE. flux-kvs(1) runs a KVS 'COMMAND'. The possible commands and their arguments are described below.