I'm working on a project to use GlusterFS as the backend for email storage to replace the current NFS implementation. The goal is to configure GlusterFS w/AFR to replicate the files across all 3 storage nodes. Each storage node will also act a an email server configured behind a load balancer running Sendmail, Maildrop, and Courier-Imap. <br>
<br>Main issue so far seems to be related with Courier-Imap in that when moving messages between IMAP folders some messages are duplicated with the io-threads enabled on the client side. Issue looks to be on the Courier-IMAP side though I haven't seen this with NFS and the duplicate messages within the Maildir have unique file names. <br>
<br>Any other simular experiences with email services backended with GlusterFS? <br><br>Node test hardware x 3:<br>Quad core Xeon 2Ghz w/ 4x7200rpm SATA drives.<br>Raid5 across all 4 drives. (Raid0 will also be tested if additional speed is necessary)<br>
8Gb Ram<br><br>Network: Currently 100Mbit though production will be 1Gbit.<br><br>Os: Debian Etch (2.6.18-6-686-bigmem)<br>GlusterFS: 1.3.12<br>Fuse: 2.7.3glfs10<br>Courier-imap 4.1.1.20060828-5<br><br>Partition Layout:<br>
sda1 --> Os (ext3)<br>sda2 --> Swap<br>sda5 --> glusterfs_data (ext3)<br><br>GlusterFS patched Fuse kernel module, util, and libraries have been installed on each of my 3 storage nodes.<br><br>Here is the basics of my Gluster configuration.<br>
Server: Brick --> TCP<br>Client: Bricks --> AFR --> io-thread --> write-behind --> io-cache --> read-ahead<br><br>Follow the Pastebin URL for my raw config file: <br><a href="http://glusterfs.pastebin.com/f7814657c">http://glusterfs.pastebin.com/f7814657c</a><br>
<br>Any suggestions? <br><br>-- Cory<br><br>