Tuesday 03 August 2010 12:00:36 pm

I see no reason why it wouldn't work, as simple as that. Not optimal, but this would work, I think. How many servers do you have in mind ?

Depending on the expected traffic, you might wanna look carefully into the performances of your setup, and tune it accordingly... the knowledge about software optimization for windows might not be very very heavy in the community though, but it's worth a try :)

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

Wednesday 04 August 2010 12:52:38 am

The problem we have had is that when following the instructions in the technical manual we get to the step for setting up the clustering and try running clusterize.php this comes back with an error

This then causes an error which breaks the whole site

D:\inet\http\oagaviation.com\ezpublish>php bin\php\clusterize.php -s eng
This script will now copy your files and/or images to database.
You have 10 seconds to break the script (press Ctrl-C).
This 1mClustering settings specified incorrectly or the chosen file handler is ezfs.

With error "Class 'ezdb' as defined in setting file.ini [ClusteringSettings] FileHandler could not be autoloaded. Did you remember to run bin/php/ezpgenerateautoloads.php after you added extension(s)?" in var/log/error.log

We have the ezdb class referenced in the autoload\ezp_kernel.php file so the system should be able to find it

When you try to access any page within the default site from a web browser we get a "Unexpected error, the message was : Access to non-public constructor of class eZDB in D:\inet\http\oagaviation.com\ezpublish\lib\ezutils\classes" in the var/log/error.log

We have had clustering work in version 4.2 on windows using ezdb as the filehandler and mysql as the db.

Wednesday 04 August 2010 3:17:11 am

hi Bertrand

ezpublish\settings\override\file.ini.append.php

is as below with obvious changes for sensitive data

<?php /* #?ini charset="utf-8"?
[ClusteringSettings]
FileHandler=ezdb
DBBackend=mysql
DBHost=host.address
DBPort=3306
DBSocket=
DBName=database_name
DBUser=user_name
DBPassword=password
DBChunkSize=65535
*/ ?>

I have checked the cluster db is the same db as used for the instance of ez publish and so is accessible using host config / credentials

Wednesday 04 August 2010 5:34:00 am

The configuration you have experimented with is the correct one. We now use class autoloading, and therefore require class names to be used instead of handler names.

Your problem is a different one; ezjscore requires specific cluster rewrite rules in order to serve packed CSS & JS files. See this issue for a solution: http://issues.ez.no/16456.

P.S. You would have experienced the exact same issue on linux. You can also find some details about that on the official online doc: http://ez.no/doc/ez_publish/technical_manual/4_x/features/clustering/setting_it_up_for_an_ezdfsfilehandler#eztoc109664_7.

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

Wednesday 04 August 2010 7:11:26 am

Could you set the thread's status to resolved then ? :-)

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier