Mod cluster mod manager Configuration: Difference between revisions
Jump to navigation
Jump to search
(13 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
* [[mod_cluster Concepts#mod_manager|mod_manager]] | * [[mod_cluster Concepts#mod_manager|mod_manager]] | ||
* [[Mod_cluster_Configuration#httpd_Configuration_Reference|mod_cluster Configuration]] | |||
= | =Overview= | ||
For concepts related to mod_manager, see [[Mod_cluster_Concepts#mod_manager|mod_cluster Concepts - mod_manager]]. | |||
=Reference= | |||
==MemManagerFile== | ==MemManagerFile== | ||
<tt>MemManagerFile</tt> is the | <tt>MemManagerFile</tt> 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 <tt>$server_root/logs/</tt>. | ||
'''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 <tt>$server_root/logs/</tt> is counterintuitive. mod_cluster should be configured to write those files in <tt>/etc/httpd/run</tt>. | |||
==ManagerBalancerName== | |||
The name for the balancer when the backend nodes do not provide a balancer name. The default value is <tt>mycluster</tt>. | |||
==EnableMCPMReceive== | |||
==Maxcontext== | |||
==Maxnode== | |||
==Maxhost== | |||
==Maxsessionid== | |||
==MaxMCMPMaxMessSize== | |||
==PersistSlots== | |||
When set to "on", [[Mod_cluster_Concepts#Worker_Node|nodes]], [[Mod_cluster_Concepts#Alias|aliases]] and [[Mod_cluster_Concepts#Context|contexts]] are persisted in files. The default value is "off". | |||
For more details related to PersistSlots, see [[Mod_cluster_Concepts#PersistSlots|mod_cluster Concepts - PeristSlots]]. | |||
Example: | |||
<pre> | |||
<IfModule manager_module> | |||
... | |||
PersistSlots on | |||
... | |||
</IfModule> | |||
</pre> | |||
==CheckNonce== | |||
==AllowDisplay== | |||
==AllowCmd== | |||
==ReduceDisplay== | |||
==SetHandler mod_cluster-manager== |
Latest revision as of 18:40, 19 October 2016
Internal
Overview
For concepts related to mod_manager, see mod_cluster Concepts - mod_manager.
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.
EnableMCPMReceive
Maxcontext
Maxnode
Maxhost
Maxsessionid
MaxMCMPMaxMessSize
PersistSlots
When set to "on", nodes, aliases and contexts are persisted in files. The default value is "off".
For more details related to PersistSlots, see mod_cluster Concepts - PeristSlots.
Example:
<IfModule manager_module> ... PersistSlots on ... </IfModule>