just to point out more weirdness: root at sum1-gstore02 nichols2]# gluster volume geo-replication gstore status MASTER SLAVE STATUS -------------------------------------------------------------------------------- gstore gluster://ox60-gstore01:gstore-rep OK [root at sum1-gstore02 nichols2]# gluster volume geo-replication gstore gluster://ox60-gstore01:gstore-rep stop geo-replication session between gstore & gluster://ox60-gstore01:gstore-rep not active geo-replication command failed [root at sum1-gstore02 nichols2]# gluster volume geo-replication gstore gluster://ox60-gstore01:gstore-rep config gluster_log_file: /var/log/glusterfs/geo-replication/gstore/gluster%3A%2F%2F10.242.64.121%3Agstore-rep.gluster.log ssh_command: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem remote_gsyncd: /usr/libexec/glusterfs/gsyncd state_file: /var/lib/glusterd/geo-replication/gstore/gluster%3A%2F%2F10.242.64.121%3Agstore-rep.status gluster_command_dir: /usr/sbin/ pid_file: /var/lib/glusterd/geo-replication/gstore/gluster%3A%2F%2F10.242.64.121%3Agstore-rep.pid log_file: /var/log/glusterfs/geo-replication/gstore/gluster%3A%2F%2F10.242.64.121%3Agstore-rep.log gluster_params: xlator-option=*-dht.assert-no-child-down=true is there really no simple way to turn this off and start fresh? On Fri, Jan 4, 2013 at 10:39 AM, Matthew Nicholson <matthew_nicholson at harvard.edu> wrote: > Oh further more, the slave as listed in the info file are things like: > > slave2=6456206b-fe19-4b65-b7ab-0c9e7ce6221e:ssh://gstore-rep:/gstore-rep > > but: > > gluster volume geo-replication gstore gstore-rep:/gstore-rep stop > geo-replication session between gstore & gstore-rep:/gstore-rep not active > geo-replication command failed > > and > > gluster volume geo-replication gstore gluster://gstore-rep:/gstore-rep stop > geo-replication session between gstore & gstore-rep:/gstore-rep not active > geo-replication command failed > > BUT: > > gluster volume geo-replication gstore gluster://gstore-rep:/gstore-rep stop > geo-replication session between gstore & > gluster://gstore-rep:/gstore-rep not active > geo-replication command failed > [root at sum1-gstore01 ~]# gluster volume geo-replication gstore > gluster://gstore-rep:/gstore-rep config > gluster_log_file: > /var/log/glusterfs/geo-replication/gstore/gluster%3A%2F%2F10.242.64.125%3A%2Fgstore-rep.gluster.log > ssh_command: ssh -oPasswordAuthentication=no > -oStrictHostKeyChecking=no -i > /var/lib/glusterd/geo-replication/secret.pem > session_owner: b5532175-bf49-413b-b0d7-b834ee9ec619 > remote_gsyncd: /usr/libexec/glusterfs/gsyncd > state_file: /var/lib/glusterd/geo-replication/gstore/gluster%3A%2F%2F10.242.64.125%3A%2Fgstore-rep.status > gluster_command_dir: /usr/sbin/ > pid_file: /var/lib/glusterd/geo-replication/gstore/gluster%3A%2F%2F10.242.64.125%3A%2Fgstore-rep.pid > log_file: /var/log/glusterfs/geo-replication/gstore/gluster%3A%2F%2F10.242.64.125%3A%2Fgstore-rep.log > gluster_params: xlator-option=*-dht.assert-no-child-down=true > > so, its got a config! > > I know much of this coem form the gsync.conf file, but i'm not clear > on how safe this is to edit, or how to get that sync'd properly among > the nodes that make up this volume... > > > > On Fri, Jan 4, 2013 at 10:26 AM, Matthew Nicholson > <matthew_nicholson at harvard.edu> wrote: >> I've got a bunch, but I'll start with my current one: >> >> [root at sum1-gstore01 ~]# gluster volume geo-replication gstore status >> MASTER SLAVE >> STATUS >> -------------------------------------------------------------------------------- >> >> >> but ps axf |grep gsync shows lots of procs, and >> /var/lib/glusterd/vols/gstore/info >> >> shows a couple slave entires. >> >> >> trying to turn off geo indexing yeilds: >> >> [root at sum1-gstore01 ~]# gluster volume set gstore geo-replication.indexing off >> geo-replication.indexing cannot be disabled while geo-replication sessions exist >> Set volume unsuccessful >> >> so, my question is, how to do i stop these outright? >> >> I'm been pinging IRC, but its pretty dead in there, and attempts to >> subscribe to this list have been failing too.... >> >> >> >> >> >> -- >> Matthew Nicholson >> matthew_nicholson at harvard.edu >> Research Computing Specialist >> FAS Research Computing >> Harvard University > > > > -- > Matthew Nicholson > matthew_nicholson at harvard.edu > Research Computing Specialist > FAS Research Computing > Harvard University -- Matthew Nicholson matthew_nicholson at harvard.edu Research Computing Specialist FAS Research Computing Harvard University
