if this feature is not stable, than this should be documented, for
example there: http://www.gluster.org/docs/index.php/Translators_v2.0
this will avoid lot of trouble using glusterfs.
Thanks!
Maris Ruskulis wrote:
Thank You, for reply! As You can see from config, ping-timeout is
not set - default
Jasper
Jasper van Wanrooy - Chatventure BV
Technical Manager
T: +31 (0) 6 47 248 722
E: jvanwanr...@chatventure.nl
W: www.chatventure.nl
- Original Message -
From: Maris Ruskulis ma...@chown.lv
To: gluster-users@gluster.org
Sent: Friday, 29 May, 2009 10:11:45 GMT +01:00 Amsterdam / Berlin
it on a 64bit platform. Is
that an option?
Best Regards Jasper
On 28 mei 2009, at 09:36, Maris Ruskulis wrote:
Hello!
After upgrade to version 2.0, now using 2.0.1, I'm experiencing
problems with glusterfs stability.
I'm running 2 node setup with cliet side afr, and glusterfsd also is
running
Hello!
Currently trying to mograte from 1.3 to glusterfs-2.0, as it is now
stable. When I start node1 I can access glusterfs, but if I start second
one, than trouble comes. Before 1.3 version worked fine.
this is what i have in logs:
fixed, incorrect volume was exported to afr
Maris Ruskulis wrote:
Hello!
Currently trying to mograte from 1.3 to glusterfs-2.0, as it is now
stable. When I start node1 I can access glusterfs, but if I start
second one, than trouble comes. Before 1.3 version worked fine.
this is what i have
