Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Configuring Remote Management and Monitoring on a Cassandra Node With JConsole

DZone's Guide to

Configuring Remote Management and Monitoring on a Cassandra Node With JConsole

Learn how to set up remote management to for your Cassandra nodes with a few easy commands.

· Database Zone ·
Free Resource

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

Want to get remote management up and running? It's easy. Just follow along.

In your cassandra-env.sh set:

LOCAL_JMX=no

If you want username and password security, keep the default setting for JMX remote authenticate as true. Otherwise, set it to false:

JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.authenticate=false"

Note: If set to true, enter a username and password for the JMX user in the jmxremote.password.file. Follow the instructions here on how to secure that file. Setting jmxremote.authenticate to true also requires you to pass in the username and password when running a nodetool command, e.g. nodetool status -u cassandra -pw cassandra

Restart the server (if needed).

Connecting to the Node Using JConsole for Monitoring

Find the JConsole jar in your JDK_HOME/bin or JDK_HOME/lib directory. If you don’t have the Java JDK installed, it can be downloaded from the Oracle Website.

Double-click the executable jar to run it (or run it from the command line). Select “Remote Process” and enter the following connection string.

  service:jmx:rmi:///jndi/rmi://<target ip address>:7199/jmxrmi

Replace <target ip address> with the address of the machine you intend to manage or monitor.

Note: JConsole may try (and fail) to connect using SSL first. If it does, it will ask if it can connect over a non-encrypted connection. You should answer this prompt in the affirmative and you are good.

Congrats! You now have everything you need to monitor and manage a Cassandra node.

For help with how to monitor Cassandra using JMX and with interpreting the metrics see:

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

Topics:
java ,jdk ,node ,jmx ,cassandra ,command line ,connection ,jar

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}