Description of problem: All of our documentation indicates that when you create a 'transport rdma' volume that glusterd listens on port 24008, but it's only listening on port 24007. A 'transport tcp,rdma' volume is supposed to listen on 24007 and 24008 but it only listens on 24007. Additional info: [root@rhs-cli-09 ~]# gluster volume info Volume Name: rdma Type: Distribute Volume ID: e2ce6774-b763-4e10-8d98-25d3d60541a8 Status: Started Number of Bricks: 2 Transport-type: tcp,rdma Bricks: Brick1: rhs-cli-09-ib0:/var/tmp/bricks/vol Brick2: rhs-cli-10-ib0:/var/tmp/bricks/vol [root@rhs-cli-09 ~]# netstat -na | egrep tcp tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:1017 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:52766 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:38465 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:38466 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:38468 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:38469 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:49157 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:24007 0.0.0.0:* LISTEN tcp 0 0 192.168.44.109:1022 192.168.44.110:24007 ESTABLISHED tcp 0 0 127.0.0.1:1021 127.0.0.1:24007 ESTABLISHED tcp 0 36 10.19.96.21:22 10.10.55.107:34116 ESTABLISHED tcp 0 0 192.168.44.109:1023 192.168.44.109:24007 ESTABLISHED tcp 0 0 192.168.44.109:24007 192.168.44.109:1023 ESTABLISHED tcp 0 0 127.0.0.1:24007 127.0.0.1:1021 ESTABLISHED tcp 0 0 192.168.44.109:24007 192.168.44.110:1022 ESTABLISHED tcp6 0 0 :::111 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 :::34342 :::* LISTEN
I believe RDMA works as expected in current releases. Closing this bug