Appendix D. Worker node configuration
Configuration values are sent to proxies under the following conditions:
- During server startup
- When a proxy is detected through the advertise mechanism
- During error recovery when a proxy’s configuration is reset
Table D.1. Proxy Configuration Values for Tomcat
Value | Default | Description |
---|---|---|
| true | Specifies whether subsequent requests for a given session should be routed to the same node, if possible. |
| false |
Specifies whether the Apache HTTP Server proxy should remove session stickiness if the balancer is unable to route a request to the node to which it is stuck. This property is ignored if |
| true |
Specifies whether the Apache HTTP Server proxy should return an error if the balancer is unable to route a request to the node to which it is stuck. This property is ignored if |
| -1 |
Specifies the number of seconds to wait for a worker to become available to handle a request. When all the workers of a balancer are unusable, mod_cluster will retry after a while ( |
| 1 |
Specifies the number of times the Apache HTTP Server proxy will attempt to send a given request to a worker before aborting. The minimum value is |
| false | Specifies whether packet flushing is enabled or disabled. |
| -1 |
Specifies the time to wait before flushing packets. A value of |
| 10 | Time to wait (in seconds) for a pong answer to a ping. |
|
Specifies the soft maximum idle connection count. The maximum value is determined by the Apache HTTP Server thread configuration ( | |
| 60 |
Specifies the time (in seconds) idle connections persist, above the |
| -1 |
Specifies the time (in seconds) mod_cluster waits for the back-end server response before returning an error. mod_cluster always uses a |
| mycluster | Specifies the name of the load-balancer. |
|
Specifies the load balancing among |