[Bugs] [Bug 1352279] [scale]: Bricks not started after node reboot.

[bugzilla at redhat.com]

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



--- Comment #3 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14849 committed in master by Kaushal M
(kaushal at redhat.com) 
------
commit 633e6fe265bc2de42dade58dc6a15c285957da76
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Sun Jul 3 15:51:20 2016 +0530

    glusterd: compare uuid instead of hostname address resolution

    In glusterd_get_brickinfo () brick's hostname is address resolved. This
adds an
    unnecessary latency since it uses calls like getaddrinfo (). Instead given
the
    local brick's uuid is already known a comparison of MY_UUID and
brickinfo->uuid
    is much more light weight than the previous approach.

    On a scale testing where cluster hosting ~400 volumes spanning across 4
nodes,
    if a node goes for a reboot, few of the bricks don't come up. After few
days of
    analysis its found that glusterd_pmap_sigin () was taking signficant amount
of
    latency and further code walthrough revealed this unnecessary address
    resolution. Applying this fix solves the issue and now all the brick
processes
    come up on a node reboot.

    Change-Id: I299b8660ce0da6f3f739354f5c637bc356d82133
    BUG: 1352279
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/14849
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai at redhat.com>
    Reviewed-by: Samikshan Bairagya <samikshan at gmail.com>
    Reviewed-by: Kaushal M <kaushal 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=e7CGtD9XMY&a=cc_unsubscribe