[opencms-dev] OpenCMS 8.5.2 in Cluster

[Ramon Gavira Sáenz]

+1 Achim


El 31/07/2013 0:02, Achim Westermann escribió:
> Hi jmcl,
>
> no. No comments from me excluding ocee. My current company spent again
> and again and again and again and again efforts to circumvent buying
> ocee. We set up cronjobs to delete static export files on slave servers
> (which costs additional performance), I - as a former OpenCms developer
> with some insight on the internals - coded a jsp to flush the caches on
> the slave instances. And on a weekly turn someone passes by to let me
> request that special jsp to have the cache flushed. And then they tried
> to deactivate the OpenCms cache and ran into performance issues. Putting
> an external cache in front of a clustered OpenCms will even get you
> deeper into the mud.
> And then some editor did forget or not know (as they were new to our
> company) that an OpenCms cluster slave will not know about changes
> witout ocee. Did not contact me and had troubles because changes were
> not propagated. And again and again and again and again and again and
> again I keep on manually flushing the cache on the slave cluster servers
> if some editor knew that we had this "cluster - issue".
> Sum up: Those 3500 bucks spent on ocee cluster... we already lost a lot
> more of money to circumvent buying that. And we will never achieve a
> better solution because Alkacon did work on that for many years and
> constantly is fixing bugs concerning ocee cluster. This is not a fanboi
> advertisement. It's just my opinion: You will never save money by trying
> to implement your own OpenCms cluster. The only thing you will achieve
> is to increase your level of maintenance and time to web.
> In case you don't know what problems will arise when running OpenCms in
> a cluster without ocee feel free to answer.
>
> Achim
>
>
>   07/30/2013 05:13 PM, jmcl wrote:
>> I would like to use OpenCMS in cluster.
>> All I need to do is use it in a scenario where *no* content is served from
>> the export folder. All content is served directly from the OpenCMS web app
>> and is, if necessary, cached on a external cache engine like Varnish.
>> I understand that having two OpenCMS nodes may cause problems when it comes
>> to *adding* or *changing* content (at least I think there can be problems).
>> Now, as for *serving* content would this be a problem???? I don't seen what
>> problems can arise from having two OpenCMSes running at the same time, as
>> web apps that they are, and externally balanced.
>> Any comments on this, that don't directly involve the OCEE module, are
>> welcome.
>> Regards.
>>
>> J.
>>
>>
>>
>> --
>> View this message in context: http://opencms.996256.n3.nabble.com/OpenCMS-8-5-2-in-Cluster-tp23501.html
>> Sent from the OpenCMS mailing list archive at Nabble.com.
>> _______________________________________________
>> 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/cgi-bin/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/cgi-bin/mailman/listinfo/opencms-dev
>
>
>

-- 

*Ramón Gavira Sáenz*
*Socio-Director de Operaciones y Proyectos*
www.sagasoluciones.com
www.templatesaga.com
www.facebook.com/sagasoluciones
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20130731/a3c0a782/attachment.htm>