Bug 1153569

Summary:	client connection establishment takes more time for rdma only volume
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	rdma	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, vbellur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-11 10:46:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mohammed Rafi KC 2014-10-16 09:04:12 UTC

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:

Comment 1 Anand Avati 2014-10-16 09:07:50 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

Comment 2 Anand Avati 2014-10-16 09:41:58 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#2) for review on master by mohammed rafi  kc (rkavunga)

Comment 3 Anand Avati 2014-10-16 12:16:44 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#3) for review on master by mohammed rafi  kc (rkavunga)

Comment 4 Anand Avati 2014-11-17 06:45:32 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#4) for review on master by mohammed rafi  kc (rkavunga)

Comment 5 Anand Avati 2014-11-17 08:25:23 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#5) for review on master by mohammed rafi  kc (rkavunga)

Comment 6 Anand Avati 2014-11-17 08:27:17 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#6) for review on master by mohammed rafi  kc (rkavunga)

Comment 7 Anand Avati 2014-11-17 10:20:51 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#7) for review on master by mohammed rafi  kc (rkavunga)

Comment 8 Anand Avati 2014-11-17 18:26:30 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#8) for review on master by mohammed rafi  kc (rkavunga)

Comment 9 Anand Avati 2014-11-17 19:17:10 UTC

REVIEW: http://review.gluster.org/8934 (rdma: client connection establishment takes more time) posted (#9) for review on master by mohammed rafi  kc (rkavunga)

Comment 10 Anand Avati 2014-11-18 08:50:18 UTC

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>

Comment 11 Mohammed Rafi KC 2015-05-11 10:46:39 UTC

available in release-3.6.2 onwards