Hi all, Besides our negative experience about this topic, there's this post: http://community.gluster.org/q/how-i-can-troubleshoot-rdma-performance-issues-in-3-3-0/ So it's normal that version 3.3 does not work with transport rdma. Best regards, Samuel. On 30 December 2012 14:44, Ayelet Shemesh <shemesh.ayelet at gmail.com> wrote: > Hi, > > I've recently install glusterfs on a cluster of several machines, and > although it works very nicely when I use TCP connections I completely fail > to use RDMA connections. > > I have 10 machines with IB NICs, and RDMA does work between them (verified > using ib_write_bw -r and several other apps). > > When I configure a volume with RDMA I have a problem with the port at the > client side. It keeps trying to get to port 24008, no matter what port the > server actually listens on (in my case 24024). > > I've tried many options to set the ports, it doesn't seem to work either > using the files under /etc/glusterd/vols/my_vol_ > name/ or using gluster volume set my_vol_name transport.socket.listen-port > (or any other option I tried). > > Any help will be appreciated. > > Thanks, > Ayelet > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130102/9ddf049c/attachment.html>
