[opencms-dev] Load balancing

[Andy Thompson]

if you can afford a hardware loadbalancer - can afford ocee.

we've been running our site much as jordi described.  personal opinion was
that it took as much time (read cost) to hack around synchronizing jsp
repositories / flushing cache etc... as it would have taken to just buy
ocee.  and i'm not happy with my hacking.

/shrug.  had to do what we did to meet deadlines...

-andy


On Sat, Mar 22, 2008 at 6:20 AM, Yves Glodt <yg at mind.lu> wrote:

> On Thursday 20 March 2008, Jordi Martí wrote:
> > Alkacon has an OCEE module just for that. But of course, it is not
> > open source. ;-))
> >
> > I've used OpenCMS the way you say, but having to sacrifice /
> > implement in other way some functionalities as:
> >       - Indexes: indexes are built in filesystem. If one instance
> indexes
> > a file, the other one won't do it, or that's what experience tells
> > me. You should manually reindex in both machines through a external
> > process. - FlexCache: if publishing happens in one machine, the other
> > one will not know that a page has been published, and cache won't be
> > invalidated. That's why I generally use a timeout based cache (cache
> > property => "timeout=10").
>
> where can this property be set?
>
> thanks for your detailed information!
> Yves
>
> >       - Config files: for example, if you import a module in one
> machine,
> > the other file "opencms-modules.xml" in the other machine won't be
> > modified. You could rsync both files or mount that directory or
> > something like that.
> >
> > There's no problem with filesystem created JSP and images, because if
> > one instance doesn't have it, it creates in on the fly, so there's no
> > problem.
> >
> > I don't remember any more, but I guess there will be. It depends on
> > what functionalities you use or want to use.
> >
> > I would be glad to hear from others what troubles they have and how
> > they solve it.
> >
> >
> >
> > JORDI MARTÍ
> > Email: jmarti AT theinit _dot_ com
> > Skype ID: jmarti.theinit
> >
> >
> >
> >
> >
> >
> > -----Mensaje original-----
> > De: opencms-dev-bounces at opencms.org
> > [mailto:opencms-dev-bounces at opencms.org] En nombre de Yves Glodt
> > Enviado el: jueves, 20 de marzo de 2008 11:31
> > Para: The OpenCms mailing list
> > Asunto: [opencms-dev] Load balancing
> >
> > Hello,
> >
> > in my setup I have a hardware loadbalancer/failover device, which
> > will balance
> > requests to two physical servers running opencms.
> >
> > These 2 servers are 1:1 copies of each other, and they connect both
> > to the *same* database (which provides failover through DRBD)
> >
> > I guess this is not a problem, to have 2 or more opencms-instances
> > from different servers connecting to the same database, or is it ???
> > :-)
> >
> > I would like to request come comments about this kind of setup...
> > What other
> >
> > ways are good for providing balancing and failover
> >
> > Regards,
> > Yves
> >
> > _______________________________________________
> > This mail is sent to you from the opencms-dev mailing list
> > To change your list options, or to unsubscribe from the list, please
> > visit http://lists.opencms.org/mailman/listinfo/opencms-dev
> >
> >
> > _______________________________________________
> > This mail is sent to you from the opencms-dev mailing list
> > To change your list options, or to unsubscribe from the list, please
> > visit http://lists.opencms.org/mailman/listinfo/opencms-dev
>
>
>
> --
> Linux 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686
>  11:19:34 up 35 min,  1 user,  load average: 0.40, 0.41, 0.36
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>



-- 
Andrew R. Thompson
Currently in N.Y *not* Consulting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20080322/6c70e229/attachment.htm>