is it safe at all,
a) a disaster, imagine CPU blows up
b) deliberately, in a control fashion
thanks everybody
___
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
On Friday 20 April 2012 10:28:35 lejeczek wrote:
is it safe at all,
a) a disaster, imagine CPU blows up
b) deliberately, in a control fashion
My first tests show that replicated volumes are still accessible when one node
is shut down hard or slow. And the changes are replicated back when the
Max out the number of IO threads and apply a patch to make gluster
more agressive about spawning threads as in this thread:
http://gluster.org/pipermail/gluster-users/2012-February/009590.html
(the above thread is actually pretty good for getting performance out
of gluster with infiniband (I use
Before I undertake this upgrade I thought I would see if anyone has any advice
on how to do this on a production system. Maybe someone has already fought
this dragon.
Current config Gluster V3.0.0. This has been in production for over 16 months:
2 servers with 8 x 2TB hard drives (bricks)