Mod cluster mod manager Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* [[mod_cluster Concepts#mod_manager|mod_manager]] | * [[mod_cluster Concepts#mod_manager|mod_manager]] | ||
* [[Mod_cluster_Configuration#httpd_Configuration_Reference|mod_cluster Configuration]] | * [[Mod_cluster_Configuration#httpd_Configuration_Reference|mod_cluster Configuration]] | ||
=Overview= | |||
For concepts related to mod_manager, see [[]]. | |||
=Reference= | =Reference= | ||
Revision as of 18:31, 10 October 2016
Internal
Overview
For concepts related to mod_manager, see [[]].
Reference
MemManagerFile
MemManagerFile is the directory mod_manager will use to store configuration, generate keys for shared memory or lock files. It must be an absolute path name. If the directory does not exist, it will be automatically created. The default value is $server_root/logs/.
Important
- It is highly recommended that the directory lives on a local drive and not an NFS share.
Possible Improvement
- Locating operational files that are not log files in $server_root/logs/ is counterintuitive. mod_cluster should be configured to write those files in /etc/httpd/run.
ManagerBalancerName
The name for the balancer when the backend nodes do not provide a balancer name. The default value is mycluster.