Best Practices for different failure scenarios?

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

 



Is there a best practices document somewhere for how to handle standard
problems that crop up?  Sort of a crib notes for things like:

1) What do you do if you see that a drive is about to fail?
2) What do you do if a drive has already failed?
3) What do you do if a peer is about to fail?
4) What do you do if a peer has failed?
5) What do you do to reinstall a peer from scratch (i.e. what
configuration files/directories do you need to restore to get the host
back up and talking to the rest of the cluster)?
6) What do you do with failed-heals?
7) What do you do with split-brains?

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




[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