On 03/02/17 07:25, Kotresh Hiremath Ravishankar wrote:> Hi, > > The following steps needs to be followed when a brick is added from new node on master. > > 1. Stop geo-repgeo repl which master volume had a brick removed: ~]$ gluster volume geo-replication GROUP-WORK 10.5.6.32::GROUP-WORK-Replica status MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 10.5.6.100 GROUP-WORK /__.aLocalStorages/3/0-GLUSTERs/GROUP-WORK root 10.5.6.32::GROUP-WORK-Replica 10.5.6.32 Active History Crawl 2017-02-01 15:24:05 ~]$ gluster volume geo-replication GROUP-WORK 10.5.6.32::GROUP-WORK-Replica stop Staging failed on 10.5.6.49. Error: Geo-replication session between GROUP-WORK and 10.5.6.32::GROUP-WORK-Replica does not exist. geo-replication command failed 10.5.6.49 is the brick which was added, now part of the master vol.> > 2. Run the following command on the master node where passwordless SSH > connection is configured, in order to create a common pem pub file. > > # gluster system:: execute gsec_create > > 3. Create the geo-replication session using the following command. > The push-pem and force options are required to perform the necessary > pem-file setup on the slave nodes. > > # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL create push-pem force > > 4. Start geo-rep > > Thanks and Regards, > Kotresh H R > > ----- Original Message ----- >> From: "lejeczek" <peljasz at yahoo.co.uk> >> To: gluster-users at gluster.org >> Sent: Thursday, February 2, 2017 1:14:07 AM >> Subject: [Gluster-users] should geo repl pick up changes to a vol? >> >> dear all >> >> should gluster update geo repl when a volume changes? >> eg. bricks are added, taken away. >> >> reason I'm asking is because it doe not seem like gluster is >> doing it on my systems? >> Well, I see gluster removed a node form geo-repl, brick that >> I removed. >> But I added a brick to a vol and it's not there in geo-repl. >> >> bw. >> L. >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://lists.gluster.org/mailman/listinfo/gluster-users >>
Kotresh Hiremath Ravishankar
2017-Feb-08 10:06 UTC
[Gluster-users] should geo repl pick up changes to a vol?
Hi lejeczek, Try stop force. gluster vol geo-rep <mastervol> <slavehost>::<slavevol> stop force Thanks and Regards, Kotresh H R Thanks and Regards, Kotresh H R ----- Original Message -----> From: "lejeczek" <peljasz at yahoo.co.uk> > To: "Kotresh Hiremath Ravishankar" <khiremat at redhat.com> > Cc: gluster-users at gluster.org > Sent: Tuesday, February 7, 2017 3:42:18 PM > Subject: [Gluster-users] should geo repl pick up changes to a vol? > > > > On 03/02/17 07:25, Kotresh Hiremath Ravishankar wrote: > > Hi, > > > > The following steps needs to be followed when a brick is added from new > > node on master. > > > > 1. Stop geo-rep > geo repl which master volume had a brick removed: > > ~]$ gluster volume geo-replication GROUP-WORK > 10.5.6.32::GROUP-WORK-Replica status > > MASTER NODE MASTER VOL MASTER > BRICK SLAVE USER > SLAVE SLAVE NODE STATUS > CRAWL STATUS LAST_SYNCED > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > 10.5.6.100 GROUP-WORK > /__.aLocalStorages/3/0-GLUSTERs/GROUP-WORK root > 10.5.6.32::GROUP-WORK-Replica 10.5.6.32 Active > History Crawl 2017-02-01 15:24:05 > > ~]$ gluster volume geo-replication GROUP-WORK > 10.5.6.32::GROUP-WORK-Replica stop > Staging failed on 10.5.6.49. Error: Geo-replication session > between GROUP-WORK and 10.5.6.32::GROUP-WORK-Replica does > not exist. > geo-replication command failed > > 10.5.6.49 is the brick which was added, now part of the > master vol. > > > > > > 2. Run the following command on the master node where passwordless SSH > > connection is configured, in order to create a common pem pub file. > > > > # gluster system:: execute gsec_create > > > > 3. Create the geo-replication session using the following command. > > The push-pem and force options are required to perform the necessary > > pem-file setup on the slave nodes. > > > > # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL > > create push-pem force > > > > 4. Start geo-rep > > > > Thanks and Regards, > > Kotresh H R > > > > ----- Original Message ----- > >> From: "lejeczek" <peljasz at yahoo.co.uk> > >> To: gluster-users at gluster.org > >> Sent: Thursday, February 2, 2017 1:14:07 AM > >> Subject: [Gluster-users] should geo repl pick up changes to a vol? > >> > >> dear all > >> > >> should gluster update geo repl when a volume changes? > >> eg. bricks are added, taken away. > >> > >> reason I'm asking is because it doe not seem like gluster is > >> doing it on my systems? > >> Well, I see gluster removed a node form geo-repl, brick that > >> I removed. > >> But I added a brick to a vol and it's not there in geo-repl. > >> > >> bw. > >> L. > >> _______________________________________________ > >> Gluster-users mailing list > >> Gluster-users at gluster.org > >> http://lists.gluster.org/mailman/listinfo/gluster-users > >> > >