5 Commits

Author	SHA1	Message	Date
David Disseldorp	66f92be635	pmda: handle struct latency_counter and add num_recoveries ... Rebase the CTDB PMDA from 1.0.114 to master: - Add tevent and ctdb_protocol includes - Handle latency metrics now stored under struct latency_counter - Add new metric for the num_recoveries counter (This used to be ctdb commit 2165a6f5117a71f9f97f46be9708fa34c037e17c)	2011-09-06 14:01:18 +02:00
David Disseldorp	88406169bd	pmda: Use CTDB_PATH macro for default socket path ... Also includes some code cleanup changes. (This used to be ctdb commit 80ad2979804f5bba29020ace46e114a45fa6cb66)	2011-09-06 14:01:18 +02:00
David Disseldorp	11ffbf4a58	pmda: Pull ctdb statistics once per fetch ... Currently ctdb statistics are pulled in the PMDA fetch callback, which results in a CTDB_CONTROL_STATISTICS call for each metric. Do this once per fetch instead, and have the per-metric callbacks pull data from the last counter cache. (This used to be ctdb commit 137b498c75c55c966999cd788f12ed9010cfed3a)	2011-09-06 14:01:18 +02:00
David Disseldorp	2f925f1e64	pmda: Attempt reconnects while ctdbd is unavailable ... Attempt to reconnect to ctdbd on fetch while it is unreachable. We must provide our own queue callback wrapper, as ctdb_client_read_cb() exits on transport failure. (This used to be ctdb commit 28df6fbf1273b8d095a2bc38dca6a6c35c5c31bd)	2011-09-06 14:01:18 +02:00
David Disseldorp	9699e5750d	pmda: Initial ctdb pmda check-in ... The CTDB Performance Metrics Domain Agent (PMDA) is compiled when Performance Co-Pilot (PCP) header files are present. The CTDB PMDA periodically requests runtime counters from ctdbd (similar to ctdb statistics) and exports these values via PCP for capture and charting etc. (This used to be ctdb commit fe7f69d6fc37661c2f1caa11de4ed3a7940d0a2f)	2011-09-06 14:01:18 +02:00