search for: rackerhacker

I am trying to track down a problem I reported on the list last week and discovered a new problem during my testing. If you have a four node setup with replicate/distribute and one of the nodes has a filesystem failure, the operating system will typically remount the filesystem read only. When this happens, the glusterfsd is still running on the failed machine, but i doesn't seem to

...and finally a probable candidate project came up. However, researching into the specific use case, it seems that gluster isn't really suitable for load profiles that deal with lots of concurrent small files. e.g. http://www.techforce.com.br/news/linux_blog/glusterfs_tuning_small_files http://rackerhacker.com/2010/12/02/keep-web-servers-in-sync-with-drbd-and-ocfs2/ http://bugs.gluster.com/show_bug.cgi?id=2869 http://gluster.org/pipermail/gluster-users/2011-June/007970.html The first two are rather old so maybe the situation has changed. But the bug report and mailing list issue in June ring alarm b...

Is anyone using Gluster with the Rocks cluster system? If so, do you know if there is a Roll for Gluster? Or, do you have any advice about things to do and things to avoid doing? We're considering using Gluster with Infiniband on our cluster and trying to learn whether other people have done this so we can perhaps learn from their experience. Thanks. .. Lana (lana.deere at gmail.com)

Hi all Reference: http://support.zresearch.com/community/documentation/index.php/Gluster_3.1:_Installing_GlusterFS_on_OpenSolaris I have found this guide to be too brief/terse, and have endeavoured to improve it via more of a recipie/howto approach - and possibly misunderstood the intent of the brief directions in the process. Please advise if there are any errors? Once the procedure is

Hello, I work in a hosting company, we have tens of Xen dom0 running just fine, but unfortunately we do have a few that get out of control. Reported behaviour : - dom0 uses more and more memory - no process can be found using that memory - at some point, oom killer kicks in, and kills everything, until even ssh the box becomes hard - when there is really no more process to kill, it crashes

Hi, I''m running multiple vservers and have some aspects managed via puppet. I noticed that puppetd consumes from 20 to 60 mb RAM and the longer the process runs, the more RAM it takes. It looks like 60MB is the top what I measured. Having a couple of vservers (11 in my case) this can already take up to 500MB just for puppet! I''m wondering if there''s any downside in