Re: How to manually/force remove a bad geo-rep agreement?

[Steve Dainard <sdainard@xxxxxxxxxxxxx>]

# gluster volume geo-replication rep1 gluster://10.0.11.4:/rep1 stop

geo-replication command failed

cli.log:

2014-04-24 14:08:03.916112] W [rpc-transport.c:175:rpc_transport_load] 0-rpc-transport: missing 'option transport-type'. defaulting to "socket"

[2014-04-24 14:08:03.918050] I [socket.c:3480:socket_init] 0-glusterfs: SSL support is NOT enabled

[2014-04-24 14:08:03.918068] I [socket.c:3495:socket_init] 0-glusterfs: using system polling thread

[2014-04-24 14:08:04.146710] I [input.c:36:cli_batch] 0-: Exiting with: -1

Steve Dainard 
IT Infrastructure Manager
Miovision | Rethink Traffic

Blog  |  LinkedIn  |  Twitter  |  Facebook

---

Miovision Technologies Inc. | 148 Manitou Drive, Suite 101, Kitchener, ON, Canada | N2C 1L3
This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.

On Thu, Apr 24, 2014 at 9:47 AM, Steve Dainard <sdainard@xxxxxxxxxxxxx> wrote:

Version: glusterfs-server-3.4.2-1.el6.x86_64

I have an issue where I'm not getting the correct status for geo-replication, this is shown below. Also I've had issues where I've not been able to stop geo-replication without using a firewall rule on the slave. I would get back a cryptic error and nothing useful in the logs.

# gluster volume geo-replication status

NODE                 MASTER               SLAVE                                              STATUS    

---------------------------------------------------------------------------------------------------

ovirt001.miovision.corp rep1                 gluster://10.0.11.4:/rep1                          faulty    

ovirt001.miovision.corp miofiles             gluster://10.0.11.4:/miofiles                      faulty    

# gluster volume geo-replication rep1 gluster://10.0.11.4:/rep1 start

geo-replication session between rep1 & gluster://10.0.11.4:/rep1 already started

geo-replication command failed

[root@ovirt001 ~]# gluster volume geo-replication status

NODE                 MASTER               SLAVE                                              STATUS    

---------------------------------------------------------------------------------------------------

ovirt001.miovision.corp rep1                 gluster://10.0.11.4:/rep1                          faulty    

ovirt001.miovision.corp miofiles             gluster://10.0.11.4:/miofiles                      faulty    

How can I manually remove a geo-rep agreement?

Thanks,

Steve 

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users