[Bugs] [Bug 1166515] [Tracker] RDMA support in glusterfs

[bugzilla at redhat.com]

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



--- Comment #26 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9177 committed in release-3.6 by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit 7efd84b1b743d3a91e23fd97dbf8a1d89b0d1f44
Author: Mohammed Rafi KC <rkavunga at redhat.com>
Date:   Thu Oct 16 11:28:33 2014 +0530

    rdma: client connection establishment takes more time

            Backport of http://review.gluster.org/8934

    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: I82a8a27f0e65a2e287f321e5e8292d86c6baf5b4
    BUG: 1166515
    Signed-off-by: Mohammed Rafi KC <rkavunga at redhat.com>
    Reviewed-on: http://review.gluster.org/8934
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    Tested-by: Raghavendra G <rgowdapp at redhat.com>
    Reviewed-on: http://review.gluster.org/9177
    Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.