Henning Brauer wrote:
>
> On Thu, Jan 18, 2001 at 07:35:33PM -0500, [EMAIL PROTECTED] wrote:
> > My question is, is it possible to run multiple instances
> > of qmail, sharing the same disk structure, configuration, etc..
>
> at least /var/qmail/queue/ must be local. Maildirs on NFS isn't that problem.
> I won't rely on linux NFS, but thats another thing.
>
So let's say each cluster node was using something like
/var/qmail/queue/_NODE_IP_HERE_/ on the NFS server,
it wouldn't be a problem for the delivery or the Maildirs?
If this is the case, is there a startup option I can give
to qmail-smtpd to change it's mail queue path?
(Or a simple hack)
I've taken a quick look at the qmail-smtpd man pages,
and haven't seen anything pertaining to that particular
issue. I suppose it's hardcoded.
> > That's plan A. Plan B is setting up a decicated mail
> > server, which I would like to avoid if necessary,
> > because it won't scale nearly as well.
>
> For first: for performance reasons one qmail machine _might_ be enough.
> You also might want to look at qmail-ldap with its native clustering
> support. http://www.nrg4u.com, docs at http://www.lifewithqmail.org/ldap/
> You should also spend some thoughts on your OS, the *BSDs may be much better
> choices for a high volume qmail server.
>
> --
> Henning Brauer | BS Web Services
> Hostmaster BSWS | Roedingsmarkt 14
> [EMAIL PROTECTED] | 20459 Hamburg
> http://www.bsws.de | Germany
I just took a look at the ldap solution, and I don't think it would fit
in very well with the system I'm setting up. It looks cool but
impractical.
As for the OS issue, I've had nothing but trouble with *BSDs, and where
they have failed me, linux hasn't :( (don't want to start an OS war
here, just the facts in my scenario)
What I'm after is not really a performance boost from qmail (I'm sure
it could run as a dedicated server and perform beyond expectations),
it's more of a high availability issue. I'm planning on using
a network block device on the NFS server to do a network RAID-1
for everything that is written to the server, with heartbeat
to automatically take over if the main server fails. Coupled
with the hardware raid,journaling filesystem, and the clustered servers,
I think it would be pretty hard to bring the system completely down.
(knock on head)
I've also been trying to find some documentation on this topic,
and so far the only thing I found indicates that this is a non-issue,
since tcpserver spawns a new qmail-smtpd for each incomming request.
(an archive of some discussion list)
If so, wouldn't this indicate that there aren't any concurrency
issue with the queue?
Thanks in advance
Mark Steele
VP research and development
Inet Technologies Inc.
[EMAIL PROTECTED]
