[Gluster-users] Best Practices for different failure scenarios?

Vijay Bellur vbellur at redhat.com
Fri Feb 21 13:51:35 UTC 2014

On 02/20/2014 03:52 AM, BGM wrote:
> On 19.02.2014, at 21:15, James <purpleidea at gmail.com> wrote:
>> On Wed, Feb 19, 2014 at 3:07 PM, Michael Peek <peek at nimbios.org> wrote:
>>> Is there a best practices document somewhere for how to handle standard
>>> problems that crop up?
>> Short answer, it sounds like you'd benefit from playing with a test
>> cluster... Would I be correct in guessing that you haven't setup a
>> gluster pool yet?
>> You might want to look at:
>> https://ttboj.wordpress.com/2014/01/08/automatically-deploying-glusterfs-with-puppet-gluster-vagrant/
>> This way you can try them out easily...
>> For some of those points... solve them with...
>>> Sort of a crib notes for things like:
>>> 1) What do you do if you see that a drive is about to fail?
>> RAID6
> or: zol, raidz<x>
> (open for critical commends)
> or: brick remove && brick add && volume heal
> (it's really just three commands, at least in my experience so far, touch wood)
> .
> but Michael, I appreciate your _original_ question:
> "Is there a best practice document?"
> Nope, not that I am aware of.
> .
> It might be very helpful to have a wiki next to this mailing list,
> where all the good experience, all the proved solutions for "situations"
> that are brought up here, could be gathered in a more
> permanent and straight way.

+1. It would be very useful to evolve an operations guide for GlusterFS.

> .
> To your questions I would add:
> what's best practice in setting options for performance and/or integrity...
> (yeah, well, for which use case under which conditions)
> a mailinglist is very helpful for adhoc probs and questions,
> but it would be nice to distill the knowledge into a permanent, searchable form.
> .
> sure anybody could set up a wiki, but...
> it would need the acceptance and participation of an active group
> to get best results.
> so IMO the appropriate place would be somewhere close to gluster.org?
> .

Would be happy to carry this in doc/ folder of glusterfs.git and 
collaborate on it if a lightweight documentation format like markdown or 
asciidoc is used for evolving this guide.


More information about the Gluster-users mailing list