https://bugzilla.redhat.com/show_bug.cgi?id=1323521
Nathan Scott <nathans@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |WONTFIX
Last Closed| |2016-04-03 20:39:41
--- Comment #1 from Nathan Scott <nathans@xxxxxxxxxx> ---
There's really no reason to worry about this. Yes, we can end up signaling the
local pmcd when a remote pmda fails. 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. If we add more localhost-only rules,
sure, lets look into it.
Signaling pmcd does not cause any problems, and is a very lightweight operation
when no work needs to be done. There is no reason not to run a local pmie on
every host where there is concern about pmda/domain-induced timeouts.
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).
> (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.
--
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=vYh5tQIkOH&a=cc_unsubscribe
|