Configuring a Global Shared Grid Library Directory
You can configure Engines to use a shared directory for Grid Libraries instead of Engines downloading their own copies.
To configure a global shared Grid Library directory:
| 1. | Disable Engine synchronization on the Admin > System Admin > Manager Configuration > Resource Deployment page. |
| 2. | On the Grid Components > Engines > Engine Configurations page, set the Grid Library Path to a shared directory with read-only access that is available from all Engines. |
| 3. | Unpack all necessary Grid Libraries into the shared Grid Library directory, with each library in its own subdirectory matching the archive filename. |
| 4. | Deploy the corresponding Grid Library archives to the Broker. The Broker still requires the same access to the Grid Libraries it always had, though Engines can now access them with an alternate method. |
Notes:
| • | Grid Libraries do not automatically update when using this deployment method. Manually unpack and update the shared Grid Libraries, and restart the Engines. |
| • | The shared Grid Library directory must contain both the Grid Library archive files and the extracted archives. |
| • | Permissions are not maintained in .zip archives regardless of Broker OS. |
| • | Permissions might be maintained when using .tar, .gz or .tgz Grid Libraries. |
| • | If the configuration does not maintain permissions in any container or distribution Grid Libraries, you must ensure that the executable permissions are set properly for any executed scripts. |
|
Note |
Using a global shared Grid Library directory with multiple Engines using the same network share can cause a significant drop in performance. |