On 02/13/2014 08:06 PM, Marco Zanger wrote:
Hi all,
I’m experiencing a strange issue related to both distribute and
replicate volumes. The problem is this:
I have two servers, A and B. Both share some replicate volumes and
distribute volumes, like this:
Volume Name: upload_path
Type: Replicate
Volume ID: 15ca11e2-206e-414d-8299-3ae20c54bd8a
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: <IP-A>:<some_path>/upload_path
Brick2: <IP-B>: <some_path>/upload_path
Each server mounts to self like this. In server A:
glusterfs#<IP_A>:upload_path on <some_path>/upload_path type fuse
(rw,default_permissions,allow_other,max_read=131072)
I’ve used both glusterfs and nfs for my tests, but when server B is down
(unreachable from A) we cannot access (nor read or write) the volumes
within A.
By inaccessible state, do you refer to read/write operations hanging or
erroring out? Does it stay forever in this inaccessible state? If you
check your client log files around the time server B is unreachable from
A, there might be some clues around this behavior.
-Vijay
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
