https://bugzilla.redhat.com/show_bug.cgi?id=1376856
Nathan Scott <nathans@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|Regression |
--- Comment #4 from Nathan Scott <nathans@xxxxxxxxxx> ---
(In reply to Frank Ch. Eigler from comment #2)
> > [...]
> > PMDA installation often doesn't cause a pmcd restart (just sighup) - and
> > increasingly will happen less and less as $force_restart gets slowly removed
> > from the code base, so this line of argument is flawed.
>
> Whatever shape the argument, the underlying issue is real. If pmlogconf is
> the premier way of autoconfiguring loggers, changes such as pmdas coming and
> going must be reflected in pmlogconf getting run. Whether this is done by
> pmmgr (predictably), or by pmlogger_check (unpredictably), it is worse than
> the new status quo (not at all).
I don't think you followed completely. For PMDAs configured in the ideal way
(i.e. without a pmcd-restart - i.e. all PMDAs running as $PCP_USER currently)
pmcd was not being restarted already. In this situation, the change is (and
always has been) encoded in the PDU exchange between pmcd/pmlogger, pmlogger
records a mark record, and there is no restart of pmcd, never was.
So, the assertion this is a new regression is incorrect - the pmmgr assumption
that pmcd would be restarted on PMDA install has always been incorrect.
However, this *is* fixable in pmmgr. If pmmgr maintains a connection to pmcd,
it would be able to detect both PMDA reconfiguration messages and loss of
connection to pmcd - and could act in the way you feel is desirable here.
Finally, while pmieconf does not actively probe today, there's every reason to
think it could become more host-probe-dynamic like pmlogconf in the future.
You continue to dismiss the situation where people write their own rules,
rather than use pmieconf, but in practice for many pmie deployments this is the
norm.
--
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=S3q4HKu9m9&a=cc_unsubscribe
|