Path

ezpublish / documentation / ez publish / technical manual / 4.6 / features / clustering / cluster configuration settings


Caution: This documentation is for eZ Publish legacy, from version 3.x to 6.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

Cluster Configuration Settings

The cluster settings are located in an override of your "settings/file.ini" file (most likely "settings/override/file.ini.append.php"or "settings/siteaccess/<SITE_ACCESS>/file.ini.append.php")
 When using the eZDB file handler the settings must be configured in the [ClusteringSettings] block. When using the eZDFS file handler the settings in the [eZDFSClusteringSettings] block must also be configured along with setting "FileHandler=eZDFSFileHandler" in [ClusterSettings] in the same file.
 Note: It is recommended to use a distinct database server if you are clustering for a high traffic website

[ClusteringSettings]

FileHandler

Possible configuration settings are:

  •  FileHandler=eZFSFileHandler
  •  FileHandler=eZDBFileHandler
  •  FileHandler=eZDFSFileHandler

This setting sets the cluster file handler. For more information regarding the cluster file handlers visit chapter "cluster file handlers". Since eZ Publish 4.1 the names of the file handlers have changed. For instance 'ezdb' is no longer recognised, the correct setting here would be 'eZDBFileHandler'. When using an eZ DFS File Handler please refer to the settings in [eZDFSClusteringSettings].

DBBackend

Possible configuration settings are:

  •  DBBackend=eZDBFileHandlerMysqlBackend
  •  DBBackend=eZDBFileHandlerOracleBackend

Use this setting to define the database backend used by the eZDB file handler. When using an eZDFSFileHandler please refer to the settings in [eZDFSClusteringSettings].
 For the database backend setting (DBBackend=) the previously used value "mysql" is deprecated. Possible values are "eZDBFileHandlerMysqlBackend" when using MySQL or "eZDBFileHandlerOracleBackend" when using Oracle (this will require the ezoracle extension)

DBHost

Possible configuration setting is:

  •  DBHost=<string>

Use the actual host name as value. In most cases this value will be the same as the "Server" setting specified under the [DatabaseSettings] block of your "site.ini.append.php" configuration file. When using an eZ DFS File Handler please refer to the settings in [eZDFSClusteringSettings].

Note: It is recommended to use a distinct database server if you are clustering for a high traffic website.

Default value is:

DBHost=localhost

DBPort

Possible configuration setting is:

  •  DBPort=<integer>

This setting sets which port to use. When using an eZ DFS File Handler please refer to the settings in [eZDFSClusteringSettings].

Default value is:

DBPort=3306

Note about DFS/PostgreSQL: since the default port is the MySQL one, specifying DBPort is required for PostgreSQL.

DBSocket

Possible configuration setting:

  •  DBSocket=

Make sure that the "DBSocket" setting is correct. Leave it empty if you have "Socket=disabled" under the [DatabaseSettings] block in "site.ini.append.php". When using and eZDFSFileHandler please refer to the settings in [eZDFSClusteringSettings].

Default value is:

DBSocket=

DBName

Possible configuration setting:

  •  DBName=<string>

Use the actual database name as value. In most cases this value will be the same as the "Database" setting specified under the [DatabaseSettings] block of your "site.ini.append.php" configuration file. When using an eZ DFS File Handler please refer to the settings in [eZDFSClusteringSettings].

Default value is:

DBName=cluster

DBUser

Possible configuration setting:

  •  DBUser=<string>

Use the user name as value. In most cases this value will be the same as the "User" setting specified under the [DatabaseSettings] block of your "site.ini.append.php" configuration file. When using an eZ DFS File Handler please refer to the settings in [eZDFSClusteringSettings].

Default value is:

DBUser=root

DBPassword

Possible configuration setting:

  •  DBPassword=<string>

Use the actual password as value. In most cases this value will be the same as the "Password" setting specified under the [DatabaseSettings] block of your "site.ini.append.php" configuration file. When using an eZ DFS File Handler please refer to the settings in [eZDFSClusteringSettings].

Default value is:

DBPassword=

DBChunkSize

Possible configuration setting:

  •  DBChunkSize=<integer>

This setting determines the size of the blocks (in bytes) into which files are split when they are fetched and inserted from the database. This setting is only valid when using eZDB.

Default value is:

DBChunkSize=65535

DBConnectRetries

Possible configuration setting:

  •  DBConnectRetries=<integer>

When using an eZ DFS File Handler please refer to the settings in [eZDFSClusteringSettings].

Default value is:

DBConnectRetries=3

DBExecuteRetries

Possible configuration setting:

  •  DBExecuteRetries=<integer>

When using an eZ DFS File Handler please refer to the settings in [eZDFSClusteringSettings].

Default value is:

DBExecuteRetries=20

NonExistantStaleCacheHandling

Possible values are:

  •  NonExistantStaleCacheHandling[]=wait
  •  NonExistantStaleCacheHandling[]=generate

Possible key settings are:

  •  [viewcache]
  •  [cacheblock]
  •  [misc]

This is an advanced setting and should only be customized if it is specifically required. This setting defines what happens when a requested cache file is already being generated and no expired cache file exists (for instance if the content is new).
 There are two possible values:

  •  The default value is "wait", which places the process in a wait loop for a limited time until the file is done generating.
  •  The second value is "generate" which lets the requesting process generate its own data without storing the result.

Use the [key] to define the type of cache that is impacted by the setting. The following three cache types are allowed ar key:

  •  viewcache
  •  cacheblock
  •  misc: this is used for any cache that is not viewcache nor cacheblock.

Example configuration setting is:

NonExistantStaleCacheHandling[viewcache]=wait

 [eZDFSClusteringSettings]

Specific configuration settings when using the eZ DFS File Handler. Most are similar to the ones mentioned in [ClusteringSettings], except "MountPointPath", "DBBackend" and "DBSocket".

MountPointPath

Possible configuration setting:

  •  MountPointPath=<string>

Since the eZ DFS File Handler is based on NFS, each eZ Publish installation sharing the same relational database must use the same cluster database and each should have a local mount point to the same NFS export. The location of the local mount point must be set here.

Example setting is:

MountPointPath=var/nfsmount

DBBackend

Possible configuration setting:

  •  DBBackend=eZDFSFileHandlerMySQLBackend

Use this setting to define the database back-end used by the eZ DB File Handler. Currently only MySQL is supported as database for the eZDFS file handler.

Default value is:

DBBackend=eZDFSFileHandlerMySQLBackend

DBSocket

Possible configuration setting:

  •  DBSocket=False

Default and value is:

DBSocket=False

Ester Heylen (14/09/2010 12:35 pm)

Bertrand Dunogier (02/03/2012 9:07 am)

Geir Arne Waaler, Bertrand Dunogier


Comments

There are no comments.