rantav/hector — Issue #404: Allow JmxMonitor to unregister a client monitor MBean
Author: liqweed
Created: 2012-01-29 09:42:32+00:00
State: open

We need to be able to shutdown a Cluster or an HConnectionManager and load a new one on demand. More generally we need to have control over the exposed MBeans in our server. Once a client monitor is loaded it registers as an MBean and is not unregistered on HConnectionManager's shutdown. The JMX ObjectName resolution logic (while not too complicated) is also not exposed publicly so if we want to unregister the MBean ourselves we need to duplicate that logic.

Please support a way I could unregister a registered client monitor MBean or expose the JMX ObjectName resolution logic publicly for me to use when I unregister it myself.