2009/7/31, Raghavendra G <raghavendra@xxxxxxxxxxx>:
Hi,
On Fri, Jul 31, 2009 at 12:28 PM, Yi Ling<lingyi.pro@gmail.com> wrote:
> there are 3 servers and a client in my clustered system. there are 2
> exported directories on each server, one for storage,the other for
> namespace. volume files for both servers and client are as follow.
>
> after all servers and client connecting sucessfully, i stop server 1. when i
> simply run 'ls' on mount point of the client, my computer (where client is
> running ) hang without any response to keyboard and mouse. is that a
> failure of a single point ??
Is the namespace is on server1? in that case you should get a
"Transport Endpoint not connected" within (2 * transport-timeout)
seconds.
transport-timeout is configured in client-protocol.
>
> im gussing it's a bug. anybody could tell why? thank you ~~~
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel@xxxxxxxxxx
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>
>
--
Raghavendra G
in my sheme, each server has a namespace volume. in the client volume file, i make a afr translator attach to them. the volume file of client is as follow:
################volfile begins#####################
volume client1
type protocol/client
option transport-type tcp/client
option remote-host 192.168.1.11
option remote-port 6996
option remote-subvolume brick
end-volume
volume client1-ns
type protocol/client
option transport-type tcp/client
option remote-host 192.168.1.11
option remote-port 6996
option remote-subvolume brick-ns
end-volume
volume client2
type protocol/client
option transport-type tcp/client
option remote-host 192.168.1.12
option remote-port 6996
option remote-subvolume brick
end-volume
volume client2-ns
type protocol/client
option transport-type tcp/client
option remote-host 192.168.1.12
option remote-port 6996
option remote-subvolume brick-ns
end-volume
volume client3
type protocol/client
option transport-type tcp/client
option remote-host 192.168.1.13
option remote-port 6996
option remote-subvolume brick
end-volume
volume client3-ns
type protocol/client
option transport-type tcp/client
option remote-host 192.168.1.13
option remote-port 6996
option remote-subvolume brick-ns
end-volume
volume clients-ns
type cluster/afr
subvolumes client1-ns client2-ns client3-ns
end-volume
volume unify
type cluster/unify
subvolumes client1 client2 client3
option namespace clients-ns
option scheduler rr
end-volume
################volfile ends#####################
i don't think it is wrong ~~~ if wrong, correct me~~~ thanks~~~
