I'm testing out using gluster for storing backup images. I don't have any data redundancy requirements beyond RAID, I just want the volume to still be writable when one (or more?) nodes are down. I tried it, but I'm getting a "transport endpoint is not connected" error when I try to write to a volume where not all the servers are reachable. Some writes fail, some writes succeed. I'm assuming this is because the path hash points to the missing server. Is there some way to get the client to try the write on another server? Currently I'm testing 3.4.0-0.3.alpha3 on CentOS 6.4 (i686! my vintage test servers don't do long mode unfortunately) If I missed some documentation that talks about this, please point me to it! Here are some specifics of what I tried: [root at 192.168.254.50 ~]# gluster volume info Volume Name: testvol Type: Distribute Volume ID: 45db51e0-18ed-4180-882e-f208ffa01452 Status: Started Number of Bricks: 4 Transport-type: tcp Bricks: Brick1: 192.168.254.50:/mnt/brick1 Brick2: 192.168.254.51:/mnt/brick1 Brick3: 192.168.254.50:/mnt/brick2 Brick4: 192.168.254.51:/mnt/brick2 My client has testvol mounted: 192.168.254.50:/testvol on /mnt/gluster-test type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072) I crudely killed all gluster services on 192.168.254.51 with "pkill -KILL gluster".
