Hi Bryan, here is what worries me: You start a replacement and will run until it is "complete" but after that you have to use the commit command. What happens with the changes that occur between the completed replace brick and the commit? Did you test the replace brick command while there are changes occurring on the FS? Am 25. April 2012 21:08 schrieb Philip <flips01 at googlemail.com>: > Hi Bryan, > > here is what worries me: You start a replacement and will run until it > is "complete" but after that you have to use the commit command. What > happens with the changes that occur between the completed replace > brick and the commit? Did you test the replace brick command while > there are changes occurring on the FS? > > Am 25. April 2012 07:15 schrieb Bryan Whitehead <driver at megahappy.net>: >> It is safe. >> >> On Tue, Apr 24, 2012 at 8:45 AM, Philip <flips01 at googlemail.com> wrote: >>> Hi, >>> >>> I'd like to replace servers in my cluster with the "replace brick" >>> command. I'm not sure if this command is safe to use when there are >>> changes on the FS e.g. new files or deletes. Can this command be >>> safely used under these circumstances or should I disable all writes >>> on the FS? >>> _______________________________________________ >>> Gluster-users mailing list >>> Gluster-users at gluster.org >>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
