RE: [Gluster-devel] problem when client goes down

[Antonio González]

Sorry, i forgot to say that when I say "shut down the network" I want to say
"unplugged" the cable of the client 1, the networks is operative for the
other clients and servers.

Thanks, 

-----Mensaje original-----
De: address@hidden
[mailto:address@hidden En
nombre de Antonio González
Enviado el: lunes, 14 de abril de 2008 18:51
Para: address@hidden
Asunto: [Gluster-devel] problem when client goes down

 

Hello all, the scenario is:

 

*         3 machines as server (pc1, pc2 exports three volumes (storage,
replication, namespace), pc3 exports two bricks (storage/posix).

*         Pc1 replicates pc2, pc2 replicates pc3 and pc3 replicates pc1.

*         Namespace is replicated at pc1 and pc2.

*         AFR’s and unify at client side.

*         2 machines as client.

 

 

The test is to copy a file from GlusterFS to local and shut down the network
before the copy finishes. I can see that the client who launched the command
waits until the network is operative.  I think that is normal that the
client waits a response from server (or timeout). But the problem is that if
I try to “ls” in the GlusterFS file system from other client, is blocked
also.

 

I don’t know if the configuration is not correct or if a GlusterFS problem
is.

 

Thanks…

 

 




 

 



Antonio González
Analista I+D 

Libera Networks
  C/ Marie Curie, 12 (PTA)
29590 Málaga 


address@hidden 


          tel: 
fax: 

+34902105282
+34952020438 

 



 
<http://www.libera.net/correoweb/redir.php?https://www.plaxo.com/add_me?u=51
540170138&v0=1125188&k0=1660502549> 

 <http://www.libera.net/correoweb/redir.php?http://www.plaxo.com/signature> 

 

_______________________________________________
Gluster-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/gluster-devel