https://bugzilla.redhat.com/show_bug.cgi?id=1334815
Nathan Scott <nathans@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends On| |1323521
--- Comment #1 from Nathan Scott <nathans@xxxxxxxxxx> ---
(In reply to Frank Ch. Eigler from comment #0)
> [...]
> restarting the pmda. Normally that's fine, but what if the restart fails,
> by another timeout right then?
pmie eventually notices and performs the restart more reliably? (*cough*)
> [...] but needs more thought & probably proper QA:
Yes, and certainly the latter - is this in-progress, or are you expecting
someone else to work on fixing this?
This is a regression that was introduced recently when moving away from the
pmie-based solution (at your insistence), but you seem to have left this BZ
assigned to me ... (as default owner? hence this followup - please assign to
yourself if you intend to continue working on resolving this, thanks).
Perhaps we should be adding back the more reliable pmie solution, as a safety
net to counter this class of unexpected problem.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1323521
[Bug 1323521] remote operation of pmie based pmda restarter interferes with
local pmcd
--
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=QfSFwc2GHJ&a=cc_unsubscribe
|