[Bugs] [Bug 1334270] glusterd: glusterd provides stale port information when a volume is recreated with same brick path

[bugzilla at redhat.com]

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



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14268 committed in master by Jeff Darcy
(jdarcy at redhat.com) 
------
commit 967a77ed4db0e1c0bcc23f132e312b659ce961ef
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Mon May 9 12:14:37 2016 +0530

    glusterd: search port from last_alloc to base_port

    If a brick process is killed ungracefully then GlusterD wouldn't receive a
    PMAP_SIGNOUT event and hence the stale port details wouldn't be removed
out.

    Now consider the following case:
    1. Create a volume with 1 birck
    2. Start the volume (say brick port allocated is 49152)
    3. Kill the brick process by 'kill -9'
    4. Stop & delete the volume
    5. Recreate the volume and start it. (Now the brick port gets 49153)
    6. Mount the volume

    Now in step 6 mount will fail as GlusterD will provide back the stale port
    number given the query starts searching from the base_port.

    Solution:

    To avoid this, searching for port from last_alloc and coming down to
base_port
    should solve the issue.

    Change-Id: I9afafd722a7fda0caac4cc892605f4e7c0e48e73
    BUG: 1334270
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/14268
    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: Samikshan Bairagya <samikshan at gmail.com>
    Reviewed-by: Jeff Darcy <jdarcy 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=wuYgZ7tLdy&a=cc_unsubscribe