OK, I changed my config more in line with the single-process server-side
AFR with additional clients, and when there is only one server up, I can
see the files with ls, but when I try to cat a file, I get this:
2008-05-16 11:01:28 E [tcp-client.c:190:tcp_connect] home2: non-blocking
connect() returned: 111 (Connection refused)
2008-05-16 11:01:28 E [client-protocol.c:4423:client_lookup_cbk] home2: no
proper reply from server, returning ENOTCONN
2008-05-16 11:01:28 E [afr.c:1985:afr_selfheal] home: none of the children
are up for locking, returning EIO
2008-05-16 11:01:28 E [fuse-bridge.c:692:fuse_fd_cbk] glusterfs-fuse: 179:
(12) /test => -1 (5)
However, with 2 protocol/server blocks, one for exporting storage/posix
(for other server nodes) and one for exporting cluster/afr (for
client-only machines), it all seems to work. And in the working
configuration, I am connecting to the protocol/server volume as the remote
subvolume, not one of the protocol/server's subvolumes. Attached is my
working spec file (home.vol) and the one that produces the above error
(home.vol.new).
Gordan
On Fri, 16 May 2008, gordan@xxxxxxxxxx wrote:
On Thu, 15 May 2008, Amar S. Tumballi wrote:
And are you saying that it is possible to connect via a
protocol/client volume to
a remote volume of type other than protocol/server?
Always protocol client connects to protocol server. But the 'option
remote-subvolume' will be
one of the subvolumes of server protocol. I thought that was noticeable in
all the spec file
examples given.
I see. So protocol/client's remote-subvolume should refer to a
protocol/server's subvolume, rather than the protocol/server's volume name
itself?
So, each server has to use a separate configuration file, rather than having
one spec file with multiple protocol/server volumes? Or is it supposed to be
done by having each protocol/server listen on a different port with the same
spec file?
Gordan
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
volume home1
type storage/posix
option directory /gluster/home
end-volume
volume home2
type protocol/client
option transport-type tcp/client
option remote-host 192.168.3.1
option remote-subvolume home2
end-volume
volume home
type cluster/afr
option read-subvolume home1
subvolumes home1 home2
end-volume
volume server
type protocol/server
option transport-type tcp/server
option client-volume-filename /etc/glusterfs/glusterfs-client.vol
subvolumes home home1
option auth.ip.home.allow 127.0.0.1,192.168.*
option auth.ip.home1.allow 127.0.0.1,192.168.*
end-volume
volume home1
type storage/posix
option directory /gluster/home
end-volume
volume storage-home
type protocol/server
option transport-type tcp/server
option listen-port 6996
subvolumes home1
option auth.ip.storage-home.allow 192.168.*
end-volume
volume home2
type protocol/client
option transport-type tcp/client
option remote-host 192.168.3.1
option remote-port 6996
option remote-subvolume storage-home
end-volume
volume home-afr
type cluster/afr
option read-subvolume home1
subvolumes home1 home2
end-volume
volume home
type protocol/server
option transport-type tcp/server
option listen-port 6997
option client-volume-filename /etc/glusterfs/glusterfs-client.vol
subvolumes home-afr
option auth.ip.home.allow 127.0.0.1,192.168.*
end-volume
