[Bugs] [Bug 1153569] New: client connection establishment takes more time for rdma only volume

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1153569

            Bug ID: 1153569
           Summary: client connection establishment takes more time for
                    rdma only volume
           Product: GlusterFS
           Version: mainline
         Component: rdma
          Severity: medium
          Assignee: gluster-bugs at redhat.com
          Reporter: rkavunga at redhat.com
                CC: bugs at gluster.org



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:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=m577L8EEtb&a=cc_unsubscribe