I would like to follow up on my question regarding an upgrade from 3.2.6
to 3.4.2.
Can anybody tell me whether I'm doing something completely wrong? Am I
trying to skip too many versions of gluster in my upgrade? Is CentOS 5
too old for this?
Thanks,
Dmitry
On 2/18/2014 2:51 PM, Dmitry
On 02/20/2014 03:52 AM, BGM wrote:
On 19.02.2014, at 21:15, James purplei...@gmail.com wrote:
On Wed, Feb 19, 2014 at 3:07 PM, Michael Peek p...@nimbios.org wrote:
Is there a best practices document somewhere for how to handle standard
problems that crop up?
Short answer, it sounds like
On 02/18/2014 12:42 AM, Franco Broi wrote:
On 18 Feb 2014 00:13, Vijay Bellur vbel...@redhat.com wrote:
On 02/17/2014 07:00 AM, Franco Broi wrote:
I mounted the filesystem with trace logging turned on and can see that
after the last successful READDIRP there is a lot of other
http://joejulian.name/blog/fixing-split-brain-with-glusterfs-33/
I spent 2 hours trying to work down my 4 node gluster split brain.
Above is a doc, I found helpful fro Joe Julian, and he's also very helpful
on irc #gluster room. Not sure if you have access to redhat but this pdf
is helpful
Hi, all
I'm new to gluster, and still trying to figure out whether it's suitable
for my project. Gluster has built-in failover support, which is very great,
but after reading the user manual, I found that the split-brain, one of the
most difficult problems of HA design, wasn't metioned at all.
+1
On Fri, Feb 21, 2014 at 2:26 PM, Brad Childs b...@redhat.com wrote:
I would like to announce a new project on Gluster forge - libgfapi-java-io.
This project aims at creating a Java 1.4+ interface to gluster using libgfapi
interface.
https://forge.gluster.org/libgfapi-java-io
On 02/21/2014 05:32 PM, Paul Simpson wrote:
I too would like to know about this.
I also tried this process on my 3.2.7 cluster and reported my findings
here:
http://vbellur.wordpress.com/2012/05/31/upgrading-to-glusterfs-3-3/
Why don't you try to upgrade to 3.3 first?
tamas
Amazingly setting cluster.readdir-optimize has fixed the problem, ls is still
slow but there's no long pause on the last readdir call.
What does this option do and why isn't it enabled by default?
___
From: gluster-users-boun...@gluster.org