| Name | Date | Size | |
|---|---|---|---|
| .. | 2015-03-10 18:25:17 | 31 | |
| config5.m4 | 2012-01-21 11:26:51 | 438 | |
| Makefile.in | 2008-12-01 03:55:14 | 183 | |
| mod_heartbeat.c | 2011-12-03 00:02:04 | 6.5 KiB | |
| mod_heartbeat.dsp | 2009-05-15 19:38:28 | 4.8 KiB | |
| mod_heartmonitor.c | 2015-03-10 18:25:17 | 28 KiB | |
| mod_heartmonitor.dsp | 2009-05-15 19:38:28 | 4.9 KiB | |
| NWGNUmakefile | 2011-03-18 05:56:06 | 4 KiB | |
| NWGNUmodheartbeat | 2012-08-09 02:11:09 | 4.2 KiB | |
| NWGNUmodheartmonitor | 2012-08-09 02:11:09 | 4.2 KiB | |
| README.heartbeat | 2008-12-01 03:55:14 | 996 | |
| README.heartmonitor | 2008-12-01 03:55:14 | 747 |
README.heartbeat
mod_heartbeat
Broadcasts the current Apache Connection status over multicast.
Example Configuration:
HeartbeatAddress 239.0.0.1:27999
Dependencies:
mod_status must be either a static module, or if a dynamic module, it must be
loaded before mod_heartbeat.
Consuming:
Every 1 second, this module generates a single multicast UDP packet,
containing the number of busy and idle workers.
The packet is a simple ASCII format, similiar to GET query parameters in UDP.
An Example packet:
v=1&ready=75&busy=0
Consumers should handle new variables besides busy and ready, separated by '&'
being added in the future.
Misc:
The interval of 1 seconds is controlled by the HEARTBEAT_INTERVAL
compile time define. This is not currently tunable at run time. To make this
module send the status packet more often, you must add to the CFLAGS used to
compile the module to include:
-DHEARTBEAT_INTERVAL=3
Would cause the broadcasts to be sent every 3 seconds.
README.heartmonitor
mod_heartmonitor
Collects the Apache Connection status data over multicast.
Example Configuration:
# First parameter is the interface to listen on
HeartbeatListen 239.0.0.1:27999
# Absolute path, or relative path to ServerRoot
HeartbeatStorage logs/hb.dat
Dependencies:
Due to a bug in APR's apr_socket_recvfrom, version 1.2.12 or newer must be
used:
Consuming:
This module atomically writes to the configured path, a list of servers,
along with metadata about them.
Included data about each server:
- IP Address
- Busy Slots
- Open Slots
- Last Seen
Every 5 seconds, this file will be updated with the current status of the
cluster.