>>>At the very least,
>>>establish persistence to your web servers on your load balancer so the
>>>one-web-server-at-a-time can serialize requests to the PHP session as the
>>>user
>>>makes simultaneous requests.
>>
>>Do you have any pointers of where to go read about this? I'm about to
>>start down this road and surely this problem has already been solved
>>thousands of times....
>>
> All *I* did was enable the built-in persistence in LVS with a 15-second
> timeout.
> Read up on that in the docs at linuxvirtualserver.org, I guess. I've found
> that
> to be enough to avoid the clobbering, although I suppose it'd still be
> possible to
> encounter it.
>
> [.........]
>
> Hello
>
> We have a cluster of 4 linux servers running SM without problems.
>
> 3 webservers running apache/PHP/SM and a database server running
> postgreSQL for sessions/addressbooks/userprefs.
>
> We use LVS to access the webservers so we have full
> failover/redundancy/load balancing at webserver level. The database is
> working perfect but we need to do something with it if we want to have
> an automatic failover/redundancy at this level too.
>
> We have around 450.000 logins/month, 18.000 different users, 1.800
> concurrent users in the system, 40.000.000 https requests/month and 220
> GB/month of data transfered and we are using 30-40% of our capacity at
> rush hours.
>
> The postgres database is working very well, we have around 60.000.000
> transactions every month and it works without problems. The table used
> for session data is heavy updated and it needs special care (vacuum runs
> once every hour).
I'd be interested to hear about the rest of your architecture. How many
IMAP servers? Do you use imapproxy (in front of each IMAP server
or...?)? Does the same postgres database support any of the rest of
your mail server infrastructure? What kind of horsepower do you use for
your virus/spam scanning, if any? What about your mail stores? NFS on
a different box? Does that box run anything fancy like SCSI RAID? etc...
> The only change in the SM code to save session data in a DB is a
> "require_once("db_sessions.php")" line in functions/global.php to
> include a file we have programed to define the
> "session_set_save_handler()" code used to access the database.
Huh. You should send the code along in case any one else wants to try
that. Any reason why John's solution would not work for you?
> TMP files from attachments sent via SM are saved in a partition in the
> database server, this partition is exported via NFS to the webservers.
> We are not 100% happy with this solution because NFS in linux does not
> work 100%. 'Sometimes' the data is not 100% on sync between all servers
> (gap of 1-2 sec.) and you can have a period of 1-2 seconds where one
> webserver can not find the TMP file saved by another webserver. This is
> a very small problem that we would like to fix in the future. Maybe is a
> good idea to save this tmp data in the database too?, any plans for this
> in the future? ;) we can help :)
I don't think this has been raised before. You are looking for a
database replacement for the attachments directory? I suppose there
could be an option to upload files straight to the db as blobs or
something, but thus far there has never been a need seen for this that I
am aware of. Keep in mind that some plugins (and maybe the core too)
will use the attachments directory for their own purposes too. That
could be fixed if we defined a save-file-in-attachments-dir function for
use by any code that wants to put a file there, but I'm not convinced
this is not overkill. It might be just as fruitful to determine if your
synch problems can be fixed at the source instead.
> If you need more information do not hesitate to ask us for it.
Thanks for sharing!
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
--
squirrelmail-users mailing list
Posting Guidelines:
http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines
List Address: [email protected]
List Archives:
http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users