On 29/01/15 07:29, Martins Innus wrote:
...
Based on your analysis, this is correct for the slow pmda case. I was
trying to come up with a test case to simulate this since I have not yet
been able to reproduce the case where pmcd closes the pmda, reliably. So
I had assumed that just doing a kill on the pmda would trigger the same
response. Clearly not true. But now I can use your gdb trick, thanks!
You're welcome ... just attach gdb to the running pmda process, and wait
for a request from pmcd to be routed to the pmda, wait 5secs, bingo!
But is it valid to assume that, as a separate case, pmcd should continue
to function if a pmda gets "killed" in some other way? OOM killer, some
other error?
Yes. Unless of course the OOM condition is so extreme to get pmcd killed.
The design point was that pmcd should continue to operate under extreme
circumstances, and pmdas coming and going (for whatever reason) falls
within that mantra.
If you have a counter example, I'd be interested to hear about it.
|