Daniel, I am running on Amazon EC2. In that environment, I can easily add machines but have a fixed amount of cpu, memory and disk per machine. The application I am running is Zimbra (www.zimbra.com). I am using glusterfs as a backend store for Zimbra. I houses the email store for all emails over 30 days old. As such, this is a read mostly environment. Every night backups run which read and write to glusterfs intensively using a multi-threaded java async file copier. Hard links are used as well. Glusterfs now handles this task perfectly and is very fast. I have also tested gluster for HSM tasks which move emails over 30 days old from primary storage to secondary storage. I am not running an application directly on gluster because I am concerned about latency in my enviroment. I will try to use gluster for more once AFR is stable and am looking forward to the S3 Xlator. Best, Harris ----- Original Message ----- From: "Daniel van Ham Colchete" <daniel.colchete@xxxxxxxxx> To: "gluster-devel" <gluster-devel@xxxxxxxxxx> Sent: Thursday, July 5, 2007 10:33:52 AM (GMT-0500) America/New_York Subject: Re: Which mainline to use Harry, I'm sorry for being so nosy, but could you please clarify something about your production environment? The project I have been planning for 8 months will go to production in less than 3 weeks. Because of the current AFR status I'm between Gluster+HeartBeat+DRBD or NFS+Heartbeat+DRBD (without anything like unify, witch is a minus). In the Gluster case I'll use mainline-2.5. Best regards, Daniel Colchete On 7/5/07, Harris Landgarten <harrisl@xxxxxxxxxxxxx> wrote: > > Einar, > > It depends on how you are using gluster. I am running 2.5 in a production > environment but I only use unify, posix-locks, readahead, writebehind and > io-threads. I would not use AFR yet with 2.5 since there is still some > debugging happening but it seems to be getting very close. Others may have > differing opinions. > > Best > > Harris > > ----- Original Message ----- > From: "Hans Einar Gautun" <einar.gautun@xxxxxxxxxxx> > To: gluster-devel@xxxxxxxxxx > Sent: Thursday, July 5, 2007 9:08:05 AM (GMT-0500) America/New_York > Subject: Which mainline to use > > Hi all, > For production use, which mainline should I check out? > > BTW - got this error from make when compiling mailline 2.4 right now: > ../../../libglusterfs/src/xlator.c -fPIC -DPIC -o .libs/xlator.o > ../../../libglusterfs/src/xlator.c: In function 'xlator_set_type': > ../../../libglusterfs/src/xlator.c:95: error: 'XLATORDIR' undeclared > (first use in this function) > > regards, > > -- > Einar Gautun gauhan@xxxxxxxxxxx > > Statens kartverk | Norwegian Mapping Authority > 3507 Hønefoss | NO-3507 Hønefoss, Norway > > Ph +47 32118372 Fax +47 32118101 Mob +47 92692662 > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxx http://lists.nongnu.org/mailman/listinfo/gluster-devel
