Jump to: navigation, search

Configuring UCS Monitoring and Maintenance

One UCS node must be dedicated to monitoring/maintenance activity. This node will open JMX connections. It must have connections to the applications that you want to monitor. It must not be part of the UCS cluster, but it must have the same [cassandra-keyspace] section configured in options.

To configure monitoring and maintenance:

  1. Activate a JMX port on all nodes that need to be monitored or where the maintenance task will be run:
    1. For Cassandra nodes, change either cassandra.in.bat or cassandra.in.sh to include the following options:
    2. -Dcom.sun.management.jmxremote.port=7199
      -Dcom.sun.management.jmxremote.ssl=false
      -Dcom.sun.management.jmxremote.authenticate=true
      -Dcom.sun.management.jmxremote.password.file=C:\jmxremote.password
      See https://wiki.apache.org/cassandra/JmxSecurity for password configuration.
    3. On each Cassandra node, set the environment variable LOCAL_JMX to value no.
    4. In Cassandra Resource Accesss Points (RAPs) add a JMX port corresponding to what you already configured previously (that is, 7199 in the example above).
    5. For UCS nodes, add a JMX port in the application (server tab) and use jmx as the protocol.
    UCSMonMaint1.png


  2. In Configuration Server:
    1. Enable UCS monitoring/maintenance node by adding a [monitor] section with the option enabled set to true.
    2. Create a JMX user by adding jmx-user-name with the value previously configured in the jmxremote.password file, and set its password.
    UCSMonMaint2.png


  3. Add connections to Cassandra RAPs and UCS applications. Note that configuration is dynamic.
  4. UCSMonMaint3.png
Important
There is no need to add connections to Elasticsearch nodes. This information is relayed by Cassandra nodes.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on May 18, 2018, at 07:01.