Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
References: <CADN_NJrmnqLPWYaV7GG4=XpXU7hZeoZhYh+Yoafr3W9RkszznA@mail.gmail.com>
In-Reply-To: <CADN_NJrmnqLPWYaV7GG4=XpXU7hZeoZhYh+Yoafr3W9RkszznA@mail.gmail.com>
From: Jonathan Haddad <jon@jonhaddad.com>
Date: Wed, 25 Jan 2017 16:15:58 +0000
Message-ID: <CACUnPaD-7Tw2694zYpd0eVTTLTyQ2sGvjjuv2COKz84R3ADGKw@mail.gmail.com>
Subject: Re: Expensive to run nodetool status often?
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a113dc3feef676b0546ed8cca
archived-at: Wed, 25 Jan 2017 16:16:15 -0000

--001a113dc3feef676b0546ed8cca
Content-Type: text/plain; charset=UTF-8

You're about to walk down an unfortunate path.  I strongly recommend
getting the information you need for monitoring using JMX.  That's actually
how nodetool gets all it's information.  Instead of parsing output, if you
 use JMX, you'll have access to a *ton* of useful (and some not so useful)
information.

If you aren't familiar, run Cassandra locally and type "jconsole" in your
terminal.  That'll bring up a decent GUI that you can use to browse all the
available metrics.

You can export metrics a bunch of ways.  Jolokia, mx4j, jmx_exporter (for
prometheus), and I know there's a collectd plugin but I haven't used it,
might be worth checking out or maybe someone else can weigh in.

Jon

On Wed, Jan 25, 2017 at 7:48 AM Xiaolei Li <xiaolei@sumologic.com> wrote:

> I'm planning to run "nodetool status -r" on every node every minute,
> storing the output in a file, and aggregating it somewhere else for
> monitoring.
>
> Is that a good idea?  How expensive is it to be running status every
> minute.
>
> Best,
> x.
>

--001a113dc3feef676b0546ed8cca
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">You&#39;re about to walk down an unfortunate path.=C2=A0 I=
 strongly recommend getting the information you need for monitoring using J=
MX.=C2=A0 That&#39;s actually how nodetool gets all it&#39;s information.=
=C2=A0 Instead of parsing output, if you =C2=A0use JMX, you&#39;ll have acc=
ess to a *ton* of useful (and some not so useful) information.<div><br></di=
v><div>If you aren&#39;t familiar, run Cassandra locally and type &quot;jco=
nsole&quot; in your terminal.=C2=A0 That&#39;ll bring up a decent GUI that =
you can use to browse all the available metrics. =C2=A0</div><div><br></div=
><div>You can export metrics a bunch of ways.=C2=A0 Jolokia, mx4j, jmx_expo=
rter (for prometheus), and I know there&#39;s a collectd plugin but I haven=
&#39;t used it, might be worth checking out or maybe someone else can weigh=
 in.</div><div><br></div><div>Jon</div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr">On Wed, Jan 25, 2017 at 7:48 AM Xiaolei Li &lt;<a href=3D=
"mailto:xiaolei@sumologic.com">xiaolei@sumologic.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><div dir=3D"ltr" class=3D"gmail_msg"><div =
class=3D"gmail_msg">I&#39;m planning to run &quot;nodetool status -r&quot; =
on every node every minute, storing the output in a file, and aggregating i=
t somewhere else for monitoring.</div><div class=3D"gmail_msg"><br class=3D=
"gmail_msg"></div><div class=3D"gmail_msg">Is that a good idea?=C2=A0 How e=
xpensive is it to be running status every minute.</div><br clear=3D"all" cl=
ass=3D"gmail_msg"><div class=3D"gmail_msg"><div class=3D"m_-806457306217564=
6362gmail_signature gmail_msg" data-smartmail=3D"gmail_signature"><div dir=
=3D"ltr" class=3D"gmail_msg">Best,<div class=3D"gmail_msg">x.</div></div></=
div></div>
</div>
</blockquote></div>

--001a113dc3feef676b0546ed8cca--