Details
-
Bug
-
Resolution: Fixed
-
Critical
-
16.02, 1.3.1
-
3 servers: server1, server2 and the third server with Mysql, where server1 and server2 fetch data from server3
Operating Systems: Debian 8
PHP Versions: PHP 5.6.20-0+deb8u1
Database and version: Mysql 5.5.49-0+deb8u1
Description
Using dfs configuration, it's not possible to configure cluster environment
I used the following configuration in my ezplatform.yml
ezpublish: # Repositories configuration, setup default repository to support solr if enabled repositories: default: storage: ~ search: engine: %search_engine% connection: default # Siteaccess configuration, with one siteaccess per default siteaccess: list: [site] groups: site_group: [site] default_siteaccess: site match: URIElement: 1 # System settings, grouped by siteaccess and/or siteaccess group system: default: io: metadata_handler: dfs binarydata_handler: nfs url_prefix: "storage" site_group: # These reflect the current installers, complete installation before you change them. For changing var_dir # it is recommended to install clean, then change setting before you start adding binary content, otherwise you'll # need to manually modify your database data to reflect this to avoid exceptions. var_dir: var/site # System languages. Note that by default, content, content types, and other data are in eng-GB locale, # so removing eng-GB from this list may lead to errors or content not being shown, unless you change # all eng-GB data to other locales first. languages: [eng-GB] # new doctrine connection for the dfs legacy_dfs_cluster metadata handler. doctrine: dbal: connections: dfs: driver: pdo_mysql host: 10.0.5.4 port: 3306 dbname: ezp user: ezp password: "mypassword" charset: UTF8 # declare the handlers ez_io: binarydata_handlers: nfs: flysystem: adapter: nfs_adapter metadata_handlers: transp dfs: legacy_dfs_cluster: connection: doctrine.dbal.dfs_connection
At this point, I have had a yml parsing problem, being the culprit
metadata_handlers: transp
Side note that is not on documentation
I was only able to make my cluster environment to work, adding
oneup_flysystem: adapters: nfs_adapter: local: directory: "/mnt/ezdfs/$var_dir$/$storage_dir$"
so, my final ezplatform.yml that worked was:
ezpublish: # Repositories configuration, setup default repository to support solr if enabled repositories: default: storage: ~ search: engine: %search_engine% connection: default # Siteaccess configuration, with one siteaccess per default siteaccess: list: [site] groups: site_group: [site] default_siteaccess: site match: URIElement: 1 # System settings, grouped by siteaccess and/or siteaccess group system: default: io: metadata_handler: dfs binarydata_handler: nfs url_prefix: "storage" site_group: # These reflect the current installers, complete installation before you change them. For changing var_dir # it is recommended to install clean, then change setting before you start adding binary content, otherwise you'll # need to manually modify your database data to reflect this to avoid exceptions. var_dir: var/site # System languages. Note that by default, content, content types, and other data are in eng-GB locale, # so removing eng-GB from this list may lead to errors or content not being shown, unless you change # all eng-GB data to other locales first. languages: [eng-GB] # new doctrine connection for the dfs legacy_dfs_cluster metadata handler. doctrine: dbal: connections: dfs: driver: pdo_mysql host: 10.0.5.4 port: 3306 dbname: ezp user: ezp password: "ezp" charset: UTF8 # declare the handlers ez_io: binarydata_handlers: nfs: flysystem: adapter: nfs_adapter metadata_handlers: dfs: legacy_dfs_cluster: connection: doctrine.dbal.dfs_connection oneup_flysystem: adapters: nfs_adapter: local: directory: "/mnt/ezdfs/$var_dir$/$storage_dir$"