Need to replace a brick on a failed first Gluster node

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Greg,

2012/1/22 Greg Scott <GregScott at infrasupport.com>:
> My challenge is, the hard drive at 192.168.253.1 failed. ?This was the first
> Gluster node when I set everything up.? ?I replaced its hard drive and am
> rebuilding it.? I have a good copy of everything I care about in the
> 192.168.253.2 brick.? ?My thought was, I could just remove the old
> 192.168.253.1 brick and replica, then gluster peer and add it all back
> again.

It's far more simple: if you retain the same hostname/ip address on
the new machine, you need to make sure the new glusterd has the same
UUID of the old dead one (there is a file in /etc/glusterd),
configurations are automatically synced back at the first contact with
the other active nodes.

Instead, if you replace the node with a different node with different
hostname / ip:
http://community.gluster.org/q/a-replica-node-has-failed-completely-and-must-be-replaced-with-new-empty-hardware-how-do-i-add-the-new-hardware-and-bricks-back-into-the-replica-pair-and-begin-the-healing-process/

-- 
Giovanni Toraldo - LiberSoft
http://www.libersoft.it


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux