https://bugzilla.redhat.com/show_bug.cgi?id=1323521
--- Comment #2 from Frank Ch. Eigler <fche@xxxxxxxxxx> ---
(In reply to Nathan Scott from comment #1)
> [...] We could workaround this, by
> adding knowledge to pmieconf about local pmcd vs not when generating config
> files - but its not worth it just for this rule. [...]
Yes, that would be a partial workaround.
> Signaling pmcd does not cause any problems, and is a very lightweight
> operation when no work needs to be done.
That's not obvious, if you consider a high-fanout remote-pmie installation,
where impotent remote-wannabe-SIGHUPs barrage the local pmcd. Have you tested
this scenario before making this assertion?
> There is no reason not to run a local pmie on every host where there
> is concern about pmda/domain-induced timeouts.
Wrong. One simple reason not to run a local pmie is to avoid paying its
performance cost (polling a variety of irrelevant metrics frequently &
redundantly, producing system log entries, consuming memory).
> It only happens once in a blue moon (in the relatively unlikely case where a
> pmda has failed, and people are using only the default-generated rulesets
> with remote hosts - these can be overridden if there was a genuine concern /
> actual issue here).
Your data for "blue moon" please. On moderately busy servers I overlook, 100%
of them encounter proc-pmda timeout/hangs after a few days of uptime.
Hand-editing default configuration files is not helpful advice, esp.
considering where these changes would have to be made (multiple place); the
general principle of having defaults -work- rather than have to be disabled;
the tools' tendency to regenerate configuration files periodically, overwriting
said hand-editing. Poor QoI.
> > (I remain convinced that pmda restarting ought to be performed by
> > logic within the local pmcd, and not require external imperfect assistance.)
>
> That's nice. Please send through the code implementing this & lets see if
> it can be made to work as reliably, and how much complexity it adds.
This is an inappropriate attitude.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=Vveu0NfTJu&a=cc_unsubscribe
|