pcp
[Top] [All Lists]

elasticsearch PMDA question

To: pcp@xxxxxxxxxxx
Subject: elasticsearch PMDA question
From: Alec Ten Harmsel <alec@xxxxxxxxxxxxxxxxxx>
Date: Mon, 14 Mar 2016 10:11:05 -0400
Delivered-to: pcp@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=NB MCbXG8pxr7vg3rQ1DpMil6bnE=; b=sY7t18+/bVQeVcbMFdAUx8UkCYIyuHJ3IS v21ytgSfnbSD24e1HY0c+1uYSWIy5CdjjJ4t1gv7RenFH5aa+G2JjMJtb2zTjCPM 2SAa4NWzvRs8qRAHJLe8qCugPZGg8+xReAi014AIzuYDROHiiy2lScuyAJxomowp e31wq/s7E=
User-agent: Mutt/1.5.24 (2015-08-30)
Hi,

We're using the elasticsearch PMDA to grab metrics on a small cluster.
By default, the PMDA grabs metrics for every node, even when PCP is only
running on one node. This is very slow; the PMDA has an internal timeout
of 1 second, but a request to get metrics from all nodes usually takes
2-3 seconds on our cluster.

My question is: is it default for PMDAs to grab metrics for as many
nodes as possible, or only on the node that PCP is running on? There is
an easy way to patch the PMDA to fix our problem, but it would break the
behavior the PMDA has historically had. What is the best way to go about
fixing this?

Thanks,

Alec

<Prev in Thread] Current Thread [Next in Thread>