summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSusant Palai <spalai@redhat.com>2017-05-26 15:47:47 +0530
committerShyamsundar Ranganathan <srangana@redhat.com>2017-05-26 16:31:48 +0000
commitd9a0b2fe129610474d7aaf69e34a8905795a8136 (patch)
tree7dd2065ad3f55123e48da9978f009dea6291124a
parent9dd15e9356c2fb32b73168b43ca2cb7d3263103f (diff)
Update release notes of 3.11 for Rebalance perf improvements
Updates glusterfs#155 Change-Id: Ife221f2bc6ae565064783cd447c078960ba97dba Signed-off-by: Susant Palai <spalai@redhat.com> Reviewed-on: https://review.gluster.org/17397 CentOS-regression: Gluster Build System <jenkins@build.gluster.org> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Smoke: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
-rw-r--r--doc/release-notes/3.11.0.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/release-notes/3.11.0.md b/doc/release-notes/3.11.0.md
index 2811d06ee46..e0cdeafa2fc 100644
--- a/doc/release-notes/3.11.0.md
+++ b/doc/release-notes/3.11.0.md
@@ -129,6 +129,21 @@ None.
### Performance improvements to rebalance have been made
*Notes for users:*
+Both crawling and migration improvement has been done in rebalance.
+The crawler is optimized now to split the migration load across replica and ec nodes.
+e.g. in case the replicating bricks are distributed over two nodes, then only one node used
+to do the migration. With the new optimization both the nodes divide the load among each
+other giving boost to migration performance. And also there have been some optimization
+to avoid redundant network fops.
+
+File migration now avoids syncop framework and is managed entirely by rebalance threads giving
+performance boost.
+
+There is a change to throttle settings in rebalance. Earlier user could set three values to
+rebalance which were "lazy", "normal", "aggressive", which was not flexible enough. To overcome
+that we have introduced number based throttle settings. User now can set numbers which is indication
+of the number of threads rebalance process will work with ultimately translating to the number of
+parallel migration.
*Limitations:*