Great Circle Associates Majordomo-Users
(May 2000)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Redundant Clustering & Majordomo
From: "Brian T. Huntley" <bth @ clarkson . edu>
Date: Thu, 4 May 2000 10:11:51 -0400 (EDT)
To: Ferry van Steen <fvansteen @ basix . org>
Cc: majordomo-users @ greatcircle . com
In-reply-to: <000a01bfb5a2$4312d3e0$6e0110ac@basix.org>

Ferry, 

We solved this issue by creating digests nightly w/ a cron command.
The script first checks a timestamp file.  If the file is from the current
day, the script exits.  Otherwise, it creates the digests and drops a
timestamp file in the pre-determined location.

Because we have the cron entries staggered by 20 minutes, server B won't
produce the digests if server A already has, even if more mail has come in
since the digests were created.

This method may not work if you are creating digests based only on size,
rather than only on time.

Hope this helps....

-
Best regards,
Brian

+-----------------------------------------------------------------------+
| Brian T. Huntley                         Systems and Network Engineer | 
| Campus Information Services, Clarkson University                      |
| Ph/FAX: 315.268-6723/6570                                             |
| bth@clarkson.edu                       	   www.clarkson.edu/cis |
+-----------------------------------------------------------------------+
 UNIX *is* user friendly. It's just selective about who its friends are.
        PGP Public Key available. finger bth@clarkson.edu

On Thu, 4 May 2000, Ferry van Steen wrote:

// Hi there,
// 
// we are working on building a redundant cluster as webserver. In other words we have 2 machines that will serve pages to the web and if one crashes the other takes over. These machines also will be doing load balancing so they'll both be responcible for 50% for the hits on the webpages, mail etc. They both have a partition that is an exact copy of the other machine, we do this by running intermezzo, a new tool that catches kernel calls and dupes them to the other configured machines. We've called this partition /bigdisk.
// 
// Anyways to get to the point, we also want to run majordomo on both this machines, but I was wondering if this is gonna cause any troubles with the mailing lists and/or digests. The mailinglists will be on the /bigdisk partition so both copies of majordomo will access the same lists. Since for the mailinglists the server that recieves mail starts majordomo and sends I don't think this will cause any problems, but I'm wondering what will happen with the digests? As I understand they will be send out at a particular time or when the file is full or when there are enough messages in it... Since this will be the same for both machines I am afraid both machines will send the digest and people will get the mail twice then?
// 
// Any suggestions/ideas to solve this would be greatly appreciated.
// 
// Kind regards,
// 
// Ferry van Steen
// 



References:
Indexed By Date Previous: Redundant Clustering & Majordomo
From: "Ferry van Steen" <fvansteen@basix.org>
Next: forwarding messages to different lists
From: "Brian Jones" <Brian_Jones@notes.teradyne.com>
Indexed By Thread Previous: Redundant Clustering & Majordomo
From: "Ferry van Steen" <fvansteen@basix.org>
Next: Re: Redundant Clustering & Majordomo
From: Dan Liston <dliston@netscape.com>

Google
 
Search Internet Search www.greatcircle.com