Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
2012.4, 4.7.0-dev
-
None
Description
Heavily related (i think) to another issue i added some weeks ago
http://issues.ez.no/IssueView.php?Id=19391&activeItem=11
If you want to use dfs cluster setup and you define your cluster settings per site access, eZFSFileHandler is still used in everypage.
The way to better test this is to enable kernel-clustering in your debug.ini.append.php
After setup my cluster database connection per siteacces, clusterizing and so on, i can see this in my debug
Timing: May 30 2012 09:18:46 Script start Debug: eZFSFileHandler::eZFSFileHandler <kernel-clustering> May 30 2012 09:18:46 fs::instance( 'var/ezflow_site/cache/expiry.php' ) Debug: <kernel-clustering> May 30 2012 09:18:46 dfs::ctor( 'var/ezflow_site/cache/statelimitations_0cbab7e743096d327e14367134b9873a.php' ) Debug: eZDFSFileHandler::processCache <kernel-clustering> May 30 2012 09:18:46 Processing local cache file var/ezflow_site/cache/statelimitations_0cbab7e743096d327e14367134b9873a.php Timing: May 30 2012 09:18:46 Module start 'content' Debug: <kernel-clustering> May 30 2012 09:18:46 dfs::ctor( 'var/ezflow_site/cache/user-info/1/0/user-data-10.cache.php' ) Debug: eZDFSFileHandler::processCache <kernel-clustering> May 30 2012 09:18:46 Processing local cache file var/ezflow_site/cache/user-info/1/0/user-data-10.cache.php ...
Is this ok? i don't think so...
Steps to reproduce
Do a fresh install and setup your dfs cluster defining your mounting path, database settings and so on per siteaccess.
Enable kernel-clustering
Check your debug.