Mirrored files on servers

This file system implementation keeps a copy of the files in the portal's file system on each node of the cluster, so that reading access to these files is local. For any change in the file system (addition, editing, and removal) made on a node of the cluster to be replicated to the other nodes, the cluster framework is used.

Example: Imagine that a file from the portal's file system is written on the node Server1, and later this same file is read on the other nodes of the cluster. In this case, the file would be distributed across the cluster by the cluster framework and access to this file is done in local folders, as shown in the figure below:

Preparing the file system

This file system implementation requires that the files be located in local folders on each node of the cluster, as in the list below:

• def: its root must be the folder <lumisdata>/shared/def
• data: its root must be the folder <lumisdata>/shared/data
• source: its root must be the folder <lumisdata>/shared/source
• static website directories: must be located in the same location configured in the Website Manager.