diff options
author | Shyam <srangana@redhat.com> | 2017-02-02 21:35:10 -0500 |
---|---|---|
committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2017-02-02 21:56:26 -0500 |
commit | 3d4192cb6c35e4ebd0d3e027c5c90599e700bc8a (patch) | |
tree | 96e094cb9dc6987966d88a91fca9fc34794a460c | |
parent | a69b00ae946db909bcbf43c9a80bfcb875019fb5 (diff) |
doc: Updated release notes with details about brick multiplexingv3.10.0rc0
Change-Id: Ie1230e262a3cd22feebe79d32d6bcb4f556e0bff
BUG: 1417735
Signed-off-by: Shyam <srangana@redhat.com>
Reviewed-on: https://review.gluster.org/16536
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>
-rw-r--r-- | doc/release-notes/3.10.0.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/release-notes/3.10.0.md b/doc/release-notes/3.10.0.md index ed36a9ed7c3..e3eb1ab9e25 100644 --- a/doc/release-notes/3.10.0.md +++ b/doc/release-notes/3.10.0.md @@ -12,10 +12,24 @@ of bugs that has been addressed is included further below. ### Brick multiplexing *Notes for users:* +Multiplexing reduces both port and memory usage. It does *not* improve +performance vs. non-multiplexing except when memory is the limiting factor, +though there are other related changes that improve performance overall (e.g. +compared to 3.9). + +Multiplexing is off by default. It can be enabled with + +```bash +# gluster volume set all cluster.brick-multiplex on +``` *Limitations:* +There are currently no tuning options for multiplexing - it's all or nothing. +This will change in the near future. *Known Issues:* +The only feature or combination of features known not to work with multiplexing +is USS and SSL. Anyone using that combination should leave multiplexing off. ### Support to display op-version information from clients *Notes for users:* |