On Fri, Aug 12, 2011 at 2:35 PM, Rajat Chopra <rchopra at redhat.com> wrote: > > Thank you Harsha for the quick response. > > Unfortunately, the infrastructure is in the cloud. So, I cant get the dead node's disk. > Since I have replication 'ON', there is no downtime as the brick on the second node serves well, but I want the redundancy/replication to be restored with the introduction of a new node (#3) in the cluster. One way is http://gluster.com/community/documentation/index.php/Gluster_3.2:_Brick_Restoration_-_Replace_Crashed_Server Other way is to use replace-brick. You should be able to use it even if the node is dead. > > I would hope there is a gluster command to just forget about the dead node's brick, and pick up the new brick and start replicating/serving from the new location (in conjunction with the one existing brick on the #2 node). Is that the self heal feature? I am using v3.11 as of now. > > Rajat > > > > > ----- Original Message ----- > From: "Harshavardhana" <harsha at gluster.com> > To: "Rajat Chopra" <rchopra at redhat.com> > Cc: gluster-users at gluster.org > Sent: Friday, August 12, 2011 2:06:14 PM > Subject: Re: Replace brick of a dead node > >> I have a two node cluster, with two bricks replicated, one on each node. >> Lets say one of the node dies and is unreachable. > > If you have the disk from the dead node, then all have to do is plug > it in new system and start running following commands. > > gluster volume replace-brick <volname> <old-brick> <new-brick> start > gluster volume replace-brick <volname> <old-brick> <new-brick> commit > > You don't have to migrate the data, this works as expected. > > Since you have a replicate you wouldn't see a downtime, ?but mind you > self-heal will kick in as of 3.2 it will be blocking, wait for 3.3 you > have non-blocking self-healing capabilities. > >> I want to be able to spin a new node and replace the dead node's brick to a location on the new node. > > This is out of Gluster's hand, if you already have mechanisms to > decommission a brick and reattach it on new node then above steps are > fairly simple. > > Go ahead and try it, it should work. > > -Harsha > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >
