summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorPranith Kumar K <pkarampu@redhat.com>2017-05-26 15:30:49 +0530
committerShyamsundar Ranganathan <srangana@redhat.com>2017-05-26 16:30:47 +0000
commit9dd15e9356c2fb32b73168b43ca2cb7d3263103f (patch)
tree615d741b8ffcffeaed03788a2160c5a0107f6030 /doc
parent093a22a3579bb95e79241e47090c2718801844f7 (diff)
Update release notes of 3.11 for halo replication
Updates: #199 Change-Id: I834543d7e71d9c3d84b595f7446a3e2c74f07d97 Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: https://review.gluster.org/17396 Smoke: Gluster Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes/3.11.0.md28
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/release-notes/3.11.0.md b/doc/release-notes/3.11.0.md
index 576a7f51565..2811d06ee46 100644
--- a/doc/release-notes/3.11.0.md
+++ b/doc/release-notes/3.11.0.md
@@ -136,10 +136,38 @@ None.
### Halo Replication feature in AFR has been introduced
*Notes for users:*
+Halo Geo-replication is a feature which allows Gluster or NFS clients to write
+locally to their region (as defined by a latency "halo" or threshold if you
+like), and have their writes asynchronously propagate from their origin to the
+rest of the cluster. Clients can also write synchronously to the cluster
+simply by specifying a halo-latency which is very large (e.g. 10seconds) which
+will include all bricks.
+To enable halo feature execute the following commands:
+```bash
+# gluster volume set cluster.halo-enabled yes
+```
+
+You may have to set the following following options to change defaults.
+`cluster.halo-shd-latency`: The threshold below which self-heal daemons will
+consider children (bricks) connected.
+
+`cluster.halo-nfsd-latency`: The threshold below which NFS daemons will consider
+children (bricks) connected.
+
+`cluster.halo-latency`: The threshold below which all other clients will
+consider children (bricks) connected.
+
+`cluster.halo-min-replicas`: The minimum number of replicas which are to
+be enforced regardless of latency specified in the above 3 options.
+If the number of children falls below this threshold the next
+best (chosen by latency) shall be swapped in.
+
*Limitations:*
+None
*Known Issues:*
+None
### FALLOCATE support with EC
Notes for users: