Forums / General / Cluster Cache Question

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Cluster Cache Question

« 
Previous topic
|
General
|
Next topic
 »
Author Message

Felipe Jaramillo

Friday 28 September 2007 9:17:17 am

Hello all,

We are studying using cluster solutions in some sites. The documentation page (http://ez.no/doc/ez_publish/technical_manual/3_9/features/clustering) says:

"Data that must be synchronized between the different servers is stored using the database:

* Binary files
* Image and image alias files
* Caches related to content:
o Content view cache
o Template block cache
o Expiry cache
o URL alias cache
o RSS cache
o User info cache
o Class identifier cache
o Sort key cache

Other files are stored using the filesystem, including (but not limited to):

* INI files
* Template files
* Compiled templates
* PHP files
* Log files
* Caches that are not related to content:
o Global INI cache
o INI cache
o Codepage cache
o Character transformation cache
o Template cache
o Template override cache

My question is about how these files, especially INI Files are shared or syncronized among the cluster nodes.

Does a normal cluster setup require an rsync of these files? Wouldn't it be better to store everything on the DB?

Thanks in advance! "

Regards,

Felipe

Felipe Jaramillo
eZ Certified Extension Developer
http://www.aplyca.com | Bogotá, Colombia

Xavier Dutoit

Friday 28 September 2007 9:42:48 am

Hi,


[DatabaseSettings]
DatabaseImplementation=ezmysql
Server=localhost
User=itwillbe
Password=quitedifficultto
Database=retrievefromthedb

;)

What do you have against rsync ?

http://www.sydesy.com

Felipe Jaramillo

Friday 28 September 2007 9:19:39 pm

Xavier,

Good point, it was hilarious!

This is the story: one of our clients datacenter security department decided they would not let any traffic from port 80 change any files in the filesystem, after having security problems with other web solutions.

It is pretty obvious what one would think of a security policy like this, but for now we are forced to take the time to consider how this could be achieved.

All cache that can expire or be cleared, should eventually be able to generate itself into the DB through normal traffic in port 80, while the admin area runs in a more relaxed port 8080.

The way we're doing this is to use a cluster configuration on a single server, but need to be able to persist things like INI cache, template cache and probably compiled template cache too.

Regards,

Felipe

Felipe Jaramillo
eZ Certified Extension Developer
http://www.aplyca.com | Bogotá, Colombia

André R.

Saturday 29 September 2007 3:39:51 am

Be aware of higher mysql load with the cluster setup.
Thats one reason why not everything is in db, it wouldn't make sense.

Also be aware that the cluster soulution is higly improved in 3.10, but only works in mysql now.
So since 3.10 is about to be finalised you might want to use 3.10 or 4.0 ( the php5 version) from the beginning.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom