| To: | chandana@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] Trying out ElasticSearch PMDA for the first time |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Tue, 7 Apr 2015 18:39:28 -0400 (EDT) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1428383139.24854.1.camel@xxxxxxxxxxxxx> |
| References: | <1427957070.8765.30.camel@xxxxxxxxxxxxx> <1446889888.13182385.1428377259368.JavaMail.zimbra@xxxxxxxxxx> <1428383139.24854.1.camel@xxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | b2daDVgEOCFQGsAHWSAsQ5Je+n8U+w== |
| Thread-topic: | Trying out ElasticSearch PMDA for the first time |
----- Original Message ----- > Hello Nathan, > Thanks for replying, and Happy Easter! > No problem, and thanks! > SIGHUP did not help, and the http query to localhost:9020 returns > instantly Hmm. So, the PMDA is supposed to be doing simple http requests just like your curl. We'll need to figure out where that big latency is coming from - can you try the attached patch and see what extra info appears in the log? This should help us trace it back to a specific query. It also adds in use of Kens recent more-rapid-er pmcd connection API, so we should certainly see some kind of behaviour change here - with any luck, for the better. :) (but it wont fix the underlying issue; need the extra elasticsearch.log diagnostics to discover which query is slow - assuming it is one of the http queries) cheers. -- Nathan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] ds389/ds389log: simplify metrics data structure, Marko Myllynen |
|---|---|
| Next by Date: | Re: [pcp] Trying out ElasticSearch PMDA for the first time, Paul Smith |
| Previous by Thread: | Re: [pcp] Trying out ElasticSearch PMDA for the first time, Chandana De Silva |
| Next by Thread: | Re: [pcp] Trying out ElasticSearch PMDA for the first time, Paul Smith |
| Indexes: | [Date] [Thread] [Top] [All Lists] |