Krishna,
The problem Antonio describes looks like the same problem I and Daniel described.
Unplugging one of the servers makes the whole cluster hang. I'm also still trying to figure
out what the problem exactly is. I've tried it without the unify translator, but on my cluster,
there is still a problem with the rest of the clients. They are not blocked, but I get a message that
the mountpoint is not connected (transport endpoint is not connected).
Krishna Srinivas wrote:
Hi Antonio,
Excuse us, somehow your issue was not responded to.
If I understand correctly, you are facing two problems:
1) plugging out the cable on one client will make other clients hang
2) the timeout value you specify in spec file does not reflect
in the actual timeout you see when you access glusterfs.
Is that correct? I have lost track of your setup details. Searching mail
archives did not give me the exact picture. Can you give the setup
details with config files? And also the tests?
Surely the problem you are facing should be fixed.
Regards
Krishna
On Mon, Apr 21, 2008 at 3:58 PM, Antonio González
<antonio.gonzalez@xxxxxxxxxx> wrote:
Hello all,
I have made a lot of tests over GlusterFS to verify his viability. I wrote
at this list one or two weeks ago asking about an issue with clients that
goes down and causes problems with other clients that can not access to the
Gluster file system.
Are the developers of GlusterFS noticed about this issue? I think that is a
serious problem and I need an answer to advice or not the use of GlusterFS
in a project.
I proved this issue over several scenarios (AFR/unify at server side, client
side, without AFR…), and I think that the problem is the unify translator.
I made a test with one server and two clients. Without unify translator
works fine, a client who goes down while reads or copy a file, don't affect
other clients. With the unify translator, if a client who reads/writes file
goes down causes the problem (other clients that tries an "ls" command are
blocked).
I made a test with two servers (without AFR, unify at client side), I have
localized files in each server, I try to block one server and access to a
file in the other server (cp command). I can see that the access to this
server (no blocked) is in function of the timeout option. If I don't set
timeout, the client takes 2 or 3 minutes and not finishes the command. If I
set a timeout of 20 sec the client takes 32 sec and finishes the command.
For a timeout of 40 s. the client takes 60 sec approximately.
I would like to know at least if this problem is recognized by the
developers of Gluster. They know which is problem? They working to solve
it? .
Thanks,
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
--
Met vriendelijke groet,
Guido Smit
ComLog B.V.
Televisieweg 133
1322 BE Almere
T. 036 5470500
F. 036 5470481
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.2/1388 - Release Date: 4/20/2008 3:01 PM
