blob: fd953e56b3fc11ca0961c1f5c9cb124b4d2bebf3 (
plain)
1
2
3
4
5
6
7
8
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).
|
