I have some strange problems with 1.4.qa47 using AFR I have 2 servers (config's below) that AFR eachother. when one of the servers goes down, I get strange behavior on the other one. the filesystem being AFR'ed is the user home directory (and web roots) whenevr one of the servers is down, the other one gets a "Transport endpoint is not connected" errors anytime someone tries to stat a file that doesn't exist for example. if the file /glusterfs/exists is there then you can read and do an ls on the file and all that good stuff, but if /glusterfs/nothere doesn't exist, then whenever you try to ls or even touch the file it gives the transport error this is really not handy. especially when a webserver is looking for .htaccess files which don't exist. it fails because it gets an error rather than file not found, so none of the web roots are accessible until the other server comes back online. hope that helps. config: volume home1 type storage/posix option directory /gluster/home end-volume volume posix-locks-home1 type features/posix-locks option mandatory on subvolumes home1 end-volume volume home2 type protocol/client option transport-type tcp/client option remote-host ##.##.##.## option remote-subvolume posix-locks-home1 option transport-timeout 10 atively low end-volume volume server type protocol/server option transport-type tcp/server subvolumes posix-locks-home1 option auth.addr.posix-locks-home1.allow ##.##.##.##,127.0.0.1 end-volume ### Create automatic file replication volume home type cluster/afr option read-subvolume posix-locks-home1 subvolumes posix-locks-home1 home2 end-volume
