Is gluster suitable and production ready for email/web servers?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've been leaning towards actually deploying gluster in one of my
projects for a while 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 bells.

Is gluster really unsuited for this kind of workload or have things
improved since then?


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux