| To: | Marko Myllynen <myllynen@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Handling Oracle PMDA Latencies |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 24 Mar 2016 00:39:56 -0400 (EDT) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <56F36E49.8010501@xxxxxxxxxx> |
| References: | <56F25541.9020602@xxxxxxxxxx> <874656864.33839965.1458781570723.JavaMail.zimbra@xxxxxxxxxx> <56F36E49.8010501@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | iwkA6DkDfF8zgHKVfn0/WiXgDAzpcw== |
| Thread-topic: | Handling Oracle PMDA Latencies |
----- Original Message ----- > Hi, > [...] > Hmm, ok, so if such latencies are found on further testing you're > basically saying that the answer is "fix Oracle"? Heh - not quite - in these cases we now have pmie able to indicate to pmcd that the PMDA should be restarted, once it bails out. However, the right thing is definitely *not* to try to add complex code into the PMDAs to attempt to deal with situations that we just cannot predict. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] Handling Oracle PMDA Latencies, Marko Myllynen |
|---|---|
| Next by Date: | parfait updates: agent fixes from tallpaul, Nathan Scott |
| Previous by Thread: | Re: [pcp] Handling Oracle PMDA Latencies, Marko Myllynen |
| Next by Thread: | pcp updates: more Mac OS X fallout, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |