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

[bugzilla at redhat.com]

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



--- Comment #10 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/8934 committed in master by Raghavendra G
(rgowdapp at redhat.com) 
------
commit 85e92d160bd71fdaeb3ae89d3440eec8fd438da9
Author: Mohammed Rafi KC <rkavunga at redhat.com>
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 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>

-- 
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=W5QwC8bFS6&a=cc_unsubscribe