Federated MBean Architecture
Geode uses MBeans to manage and monitor different parts of Geode. Geode’s federated MBean architecture is scalable and allows you to have a single-agent view of a Geode distributed system.
Federation of the MBeanServers means that one member, the JMX Manager Node, can provide a proxied view of all the MBeans that the MBeanServer hosts. Federation also means that operations and notifications are spread across the distributed system.
Geode federation takes care of the following functionality:
- MBean proxy creation
- MBean state propagation
- Notifications propagation
- Operation invocation
Each Geode MBean follows a particular naming convention for easier grouping. For example:
At the JMX Manager node, this MBean will be registered with GemFire/<memberId> as domain.
The following are some sample MBean names:
In its Management API, Geode provides MXBeans to ensure that any MBeans that are created are usable by any client, including remote clients, without requiring the client to access specific classes in order to access contents of the MBean.
Geode proxies are inherently local MBeans. Every Geode JMX manager member hosts proxies pointing to the local MBeans of every managed node. Proxy MBeans will also emit any notification emitted by local MBeans in managed nodes when an event occurs in that managed node.
Note: Aggregate MBeans on the JMX Manager node are not proxied.
This topic provides descriptions for the various management and monitoring MBeans that are available in Geode.
You can browse all the Geode MBeans in your distributed system by using JConsole.
Apache Geode MBeans emit notifications when specific events occur or if an alert is raised in the Geode system. Using standard JMX APIs, users can add notification handlers to listen for these events.