|Managing and Monitoring GemFire XD / Using Java Management Extensions (JMX)|
The GemFire XD management and monitoring system consists of one JMX Manager node (there should only be one) and one or more managed nodes within a distributed system. All members in the distributed system are manageable through MBeans.
The following diagram depicts the architecture of the management and monitoring system components.
In this architecture every GemFire XD member is manageable. All GemFire XD MBeans for the local GemFire XD processes are automatically registered in the Platform MBeanServer (the default MBeanServer of each JVM that hosts platform MXBeans.)
A JMX Manager node is a member that can manage other GemFire XD members—that is, other managed nodes—as well as itself. A JMX Manager node can manage all other members in the distributed system.
To convert a managed node to a JMX Manager node, you configure the GemFire XD property jmx-manager=true, in the gemfirexd.properties file, and start the member as a JMX Manager node. You start the member as a JMX Manager node when you provide --J=-Dgemfire.jmx-manager=true as an argument to either the start server or start locator command. See Starting a JMX Manager for more information.
Management and monitoring tools such as GemFire XD Pulse use JMX/RMI as the communication layer to connect to GemFire XD nodes. All GemFire XD processes by default allow JMX connections to the Platform MBeanServer from localhost.
JConsole (and other similar JMX clients that support Sun's Attach API) can connect to any local JVM without requiring an RMI connector by using the Attach API. This allows connections from the same machine.
JConsole (and other JMX clients) can connect to any JVM if that JVM is configured to start an RMI connector. This allows remote connections from other machines.
JConsole can connect to any GemFire XD member, but if it connects to a non-JMX-Manager member, JConsole only detects the local MBeans for the node, and not MBeans for the cluster.
When a GemFire XD locator or server becomes a JMX Manager for the cluster, it enables the RMI connector. JConsole can then connect only to that one JVM to view the MBeans for the entire cluster. It does not need to connect to any other JVMs, and other non-managed GemFire XD nodes do not start an RMI connector by default. The GemFire XD manager node manages the inter-JVM communication required to provide a federated view of all MBeans in the distributed system.
For information on how to configure the RMI registry and RMI connector, see Configuring RMI Registry Ports and RMI Connectors.