Bug 989532 - Dist-geo-rep : After add-brick ,no working_dir created for the added bricks
Summary: Dist-geo-rep : After add-brick ,no working_dir created for the added bricks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard:
Depends On: 984942 985236
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-29 13:12 UTC by Avra Sengupta
Modified: 2014-07-11 19:17 UTC (History)
9 users (show)

Fixed In Version: glusterfs-3.5.1
Doc Type: Bug Fix
Doc Text:
Clone Of: 985236
Environment:
Last Closed: 2014-07-11 19:17:39 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Anand Avati 2013-07-29 13:16:44 UTC 
REVIEW: http://review.gluster.org/5416 (glusterd : initiating gsyncd restart during add-brick) posted (#1) for review on master by Avra Sengupta (asengupt)
Comment 2 Anand Avati 2013-07-29 13:21:44 UTC 
REVIEW: http://review.gluster.org/5416 (glusterd : initiating gsyncd restart during add-brick) posted (#2) for review on master by Avra Sengupta (asengupt)
Comment 3 Anand Avati 2013-07-29 13:41:59 UTC 
REVIEW: http://review.gluster.org/5416 (glusterd : initiating gsyncd restart during add-brick) posted (#3) for review on master by Avra Sengupta (asengupt)
Comment 4 Anand Avati 2013-07-31 07:39:12 UTC 
REVIEW: http://review.gluster.org/5416 (glusterd : initiating gsyncd restart during add-brick) posted (#4) for review on master by Avra Sengupta (asengupt)
Comment 5 Anand Avati 2013-07-31 16:17:37 UTC 
COMMIT: http://review.gluster.org/5416 committed in master by Vijay Bellur (vbellur) 
------
commit 031b69fc7b2f26d07113aabec95662816adfad86
Author: Avra Sengupta <asengupt>
Date:   Fri Jul 26 21:45:22 2013 +0530

    glusterd : initiating gsyncd restart during add-brick
    
    During add-brick, when a new brick is added in one of the
    nodes that was already a part of the existing volume, and
    gsyncd was already running on that node, then all gsyncd
    processes running on that node, for that particular master
    and any slave sessions will be restarted
    
    If a new brick is added in a new node, then after adding the
    brick, the user has to perform the following steps:
    
    1. gluster system:: execute gsec_create
    2. gluster volume geo-replication <master-vol> <slave-vol> create push-pem force
    3. gluster volume geo-replication <master-vol> <slave-vol> start force
    
    Change-Id: I4b9633e176c80e4a7cf33f42ebfa47ab8fc283f1
    BUG: 989532
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/5416
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Amar Tumballi <amarts>
    Reviewed-by: Vijay Bellur <vbellur>
Note You need to log in before you can comment on or make changes to this bug.