summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJeff Darcy <jdarcy@redhat.com>2014-04-15 18:06:24 +0000
committerVijay Bellur <vbellur@redhat.com>2014-04-16 10:37:34 -0700
commitd6ad57239d396f31ae0cd21e2e8e5db64aae5714 (patch)
tree88bf8e50a2c47c91b95f9f8d3dd1aed526efe901
parent686ee24a80c6ee7a5135aace8c2536f2afbcf367 (diff)
doc: add documentation for NUFA feature
Change-Id: I00f1c669d4ebc61f09c50f8de4c893907f6d75c2 BUG: 1086745 Signed-off-by: Jeff Darcy <jdarcy@redhat.com> Reviewed-on: http://review.gluster.org/7489 Reviewed-by: Niels de Vos <ndevos@redhat.com> Reviewed-by: Vijay Bellur <vbellur@redhat.com> Tested-by: Vijay Bellur <vbellur@redhat.com>
-rw-r--r--doc/features/nufa.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/features/nufa.md b/doc/features/nufa.md
new file mode 100644
index 0000000..03b8194
--- /dev/null
+++ b/doc/features/nufa.md
@@ -0,0 +1,20 @@
+# NUFA Translator
+
+The NUFA ("Non Uniform File Access") is a variant of the DHT ("Distributed Hash
+Table") translator, intended for use with workloads that have a high locality
+of reference. Instead of placing new files pseudo-randomly, it places them on
+the same nodes where they are created so that future accesses can be made
+locally. For replicated volumes, this means that one copy will be local and
+others will be remote; the read-replica selection mechanisms will then favor
+the local copy for reads. For non-replicated volumes, the only copy will be
+local.
+
+## Interface
+
+Use of NUFA is controlled by a volume option, as follows.
+
+ gluster volume set myvolume cluster.nufa on
+
+This will cause the NUFA translator to be used wherever the DHT translator
+otherwise would be. The rest is all automatic.
+