Sat 27 Dec 2008 08:54:41 PM UTC, comment #1:
Moving the afr to the server side seems to have a positive impact.
=======
client:
web1:/www/photo_rolls_ite/shared_images/fredmeyer/photo_roll/p99# cat /usr/local/etc/glusterfs/glusterfs-client.vol
volume arraynas1
type protocol/client
option transport-type tcp/client
option remote-host 10.5.1.180
option remote-subvolume array
end-volume
=======
server:
[root@nas1 border.2007-12-18]# cat /usr/local/etc/glusterfs/glusterfs-server.vol
volume nas1brick1
type storage/posix
option directory /data/brick1
end-volume
volume nas1brick1p
type features/posix-locks
subvolumes nas1brick1
end-volume
volume nas1brick2
type storage/posix
option directory /data/brick2
end-volume
volume nas1brick2p
type features/posix-locks
subvolumes nas1brick2
end-volume
volume nas1-ns
type storage/posix
option directory /data/ns
end-volume
volume nas1-nsp
type features/posix-locks
subvolumes nas1-ns
end-volume
volume nas1
type cluster/unify
option namespace nas1-nsp
option scheduler rr
subvolumes nas1brick1p nas1brick2p
end-volume
volume nas2
type protocol/client
option transport-type tcp/client
option remote-host 10.10.1.185
option remote-subvolume nas2
end-volume
volume array
type cluster/afr
subvolumes nas2 nas1
option favorite-child nas2
end-volume
volume server
type protocol/server
option transport-type tcp
subvolumes array
option auth.addr.array.allow *
end-volume
|