diff options
| author | Vijay Bellur <vbellur@redhat.com> | 2013-07-25 17:12:21 +0530 |
|---|---|---|
| committer | Anand Avati <avati@redhat.com> | 2013-07-25 05:07:11 -0700 |
| commit | e9c583598b8ad58bbda15759067ff57eca619e95 (patch) | |
| tree | 3653ddaca4c2975bed44b17fc59f8ef64afcf2a1 /doc/features/rdma-cm-in-3.4.0.txt | |
| parent | 131d78dd36bac795d50fee3b04969b5ea9cb613c (diff) | |
doc: Create a features folder.
Moved rdma and bd documents to doc/features. Added a new
document on rebalance.
Change-Id: I04269202adc9605754fc29876433c88480b822a3
BUG: 811311
Signed-off-by: Vijay Bellur <vbellur@redhat.com>
Reviewed-on: http://review.gluster.org/5395
Reviewed-by: Anand Avati <avati@redhat.com>
Tested-by: Anand Avati <avati@redhat.com>
Diffstat (limited to 'doc/features/rdma-cm-in-3.4.0.txt')
| -rw-r--r-- | doc/features/rdma-cm-in-3.4.0.txt | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/features/rdma-cm-in-3.4.0.txt b/doc/features/rdma-cm-in-3.4.0.txt new file mode 100644 index 00000000000..fd953e56b3f --- /dev/null +++ b/doc/features/rdma-cm-in-3.4.0.txt @@ -0,0 +1,9 @@ +Following is the impact of http://review.gluster.org/#change,149. + +New userspace packages needed: +librdmacm +librdmacm-devel + +rdmacm needs an IPoIB address for connection establishment. This requirement results in following issues: +* Because of bug #890502, we've to probe the peer on an IPoIB address. This imposes a restriction that all volumes created in the future have to communicate over IPoIB address (irrespective of whether they use gluster's tcp or rdma transport). +* Currently client has an independence to choose b/w tcp and rdma transports while communicating with the server (by creating volumes with transport-type tcp,rdma). This independence was a byproduct of our ability use the normal channel used with transport-type tcp for rdma connectiion establishment handshake too. However, with new requirement of IPoIB address for connection establishment, we loose this independence (till we bring in multi-network support - where a brick can be identified by a set of ip-addresses and we can choose different pairs of ip-addresses for communication based on our requirements - in glusterd). |