Description of problem: For rdma type only volume client connection establishment with server takes more than three seconds. Because for tcp,rdma type volume, will have 2 ports one for tcp and one for rdma, tcp port is stored with brickname and rdma port is stored as "brickname.rdma" during pamap_sighin. During the handshake when trying to get the brick port for rdma clients, since we are not aware of server transport type, we will append '.rdma' with brick name. So for tcp,rdma volume there will be an entry with '.rdma', but it will fail for rdma type only volume. So for the next try we will not append '.rdma' and it will succeed, but the reconnection happens only after 3 seconds. In this patch for rdma only type volume we will append '.rdma' during the pmap_signin. So during the handshake we will get the correct port for first try itself Version-Release number of selected component (if applicable): all How reproducible: very Steps to Reproduce: 1.create a rdma only volume 2. start the volume 3. mount the volume Actual results: mount takes more than three seconds Expected results: mount should happens immediately. Additional info:
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#2) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#3) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#4) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#5) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#6) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#7) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#8) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#9) for review on master by mohammed rafi kc (rkavunga)
COMMIT: http://review.gluster.org/8934 committed in master by Raghavendra G (rgowdapp) ------ commit 85e92d160bd71fdaeb3ae89d3440eec8fd438da9 Author: Mohammed Rafi KC <rkavunga> Date: Thu Oct 16 11:28:33 2014 +0530 rdma: client connection establishment takes more time For rdma type only volume client connection establishment with server takes more than three seconds. Because for tcp,rdma type volume, will have 2 ports one for tcp and one for rdma, tcp port is stored with brickname and rdma port is stored as "brickname.rdma" during pamap_sighin. During the handshake when trying to get the brick port for rdma clients, since we are not aware of server transport type, we will append '.rdma' with brick name. So for tcp,rdma volume there will be an entry with '.rdma', but it will fail for rdma type only volume. So we will try again, this time without appending '.rdma' using a flag variable need_different_port, and it will succeed, but the reconnection happens only after 3 seconds. In this patch for rdma only type volume we will append '.rdma' during the pmap_signin. So during the handshake we will get the correct port for first try itself. Since we don't need to retry , we can remove the need_different_port flag variable. Change-Id: Ie8e3a7f532d4104829dbe995e99b35e95571466c BUG: 1153569 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/8934 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
available in release-3.6.2 onwards