LATEST VERSION: 8.2.6 - CHANGELOG
Pivotal GemFire® v8.2

JMX Manager Operations

JMX Manager Operations

Any member can host an embedded JMX Manager, which provides a federated view of all MBeans for the distributed system. The member can be configured to be a manager at startup or anytime during its life by invoking the appropriate API calls on the ManagementService.

You need to have a JMX Manager started in your distributed system in order to use GemFire management and monitoring tools such as gfsh and GemFire Pulse.

Note: Each node that acts as the JMX Manager has additional memory requirements depending on the number of resources that it is managing and monitoring. Being a JMX Manager can increase the memory footprint of any process, including locator processes. See Memory Requirements for Cached Data for more information on calculating memory overhead on your GemFire processes.