Greetings. I have (re) setup hosted01/hosted02 with glusterfs 3.3.0 (plus a patch for the 16 groups limitation issue we ran into before). Both nodes are using nfs mounts for the gluster data. In my limited testing here, they seem to be reasonably responsive, the 16 gid thing is fixed, and locking doesn't seem to be causing any problems. However, it would be great if a few more folks hit them and tried to cause them to break. :) You can test most easily by just changing your /etc/hosts: # hosted 02 #66.135.62.187 fedorahosted.org git.fedorahosted.org svn.fedorahosted.org bzr.fedorahosted.org # hosted 01 #66.135.62.201 fedorahosted.org git.fedorahosted.org svn.fedorahosted.org bzr.fedorahosted.org Any scm changes you make will just be overwritten when next I sync from hosted03 to the new pair. However, if you change trac tickets, those will cause emails to be sent (as it sends by directly connecting to bastion). If folks could try testing and see if you can cause any locking issues or notice any performance problems that would be great. Thanks, kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
