Tag Info

New answers tagged

1

Gluster would solve the problem you have because it can hold the locks, propagate changes - delete the file on all other nodes, but it may add additional latency that can be a problem for a webserver. The next alternative is DRBD+OCFS2 or GFS, but that's probably more complex as with gluster you are using the underlying filesystem - it doesn't operate at the ...


1

GlusterFS is hard to deploy. For web data, file sync level like Unison is much easier to deploy and maintenance. DRBD is a perfect solution for keep data sync at block level. But you have to format them to special format like OCFS2 or something similar.


0

In the /etc/rc.d directory there is also a file called rc.local, which is the rc file that init will run after everything else is done. So you could take off that from default startup sequence and put under rc.local chkconfig httpd off echo "/etc/init.d/httpd start" >> /etc/init.d/rc.local this should work for above scenario unless you have some ...


0

You can use the parameters storage.owner.gid storage.owner.uid glusterfs 3.5.0 built on May 1 2014 11:57:24 Option: storage.owner-uid Default Value: (null) Description: Support for setting uid of brick's owner Option: storage.owner-gid Default Value: (null) Description: Support for setting gid of brick's owner Cheers.


0

You should use the options below so that when the glusterfs mount the volume the permissions are according to your needs storage.owner-gid storage.owner-uid ex: gluster volume VOL-NAME set storage.owner-gid 100


1

Depends on source of your data. If data you want to sync is generated somewhere else (developers workstation, etc) and only distributed to clients via those 3 servers, I would recommend to push the data to each of three servers via rsync, or some CI tool like Jenkins, keeping the files on local disks of each server. If the data is generated and served by ...


4

According to the upstart cookbook/intro linked here, upstart will emit a 'filesystem' event when all mounts are completed. You should be able to "start on filesystem" the required service to achieve what you're looking for, unless you're only wanting certain (but not all) filesystems to be mounted prior to service invocation?


0

Perhaps you installed glusterfs-client from Ubuntu's repo's before you setup your PPA? Therefor, you wouldn't have the up to date version.


4

This seems to be a known issue which according to README.Ubuntu should be fixed in Ubuntu 14.04. A possible workaround for earlier Ubuntu versions could be to defer the volume mount with a custom upstart job after the GlusterFS server gets started.



Top 50 recent answers are included