hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3780) Expose JMX Management of at least the JVM
Date Mon, 29 Dec 2014 20:00:13 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack resolved HBASE-3780.
    Resolution: Not a Problem

Resolving as not a problem.  In jvisualvm, the memory and threading mbeans have active operations
including invoking GC, the root reason for the filing of this issue.

> Expose JMX Management of at least the JVM
> -----------------------------------------
>                 Key: HBASE-3780
>                 URL: https://issues.apache.org/jira/browse/HBASE-3780
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: stack
> IIRC, you can run a full gc via JMX JVM management bean.  We should expose JMX management
of JVM at least and then down the road of HBase functions.  We want the full gc to implement
suggestion of todds over in HBASE-3441 where we'd have a regionserver unload its regions gracefully,
we'd then do a full gc, then we'd move the regions back on again. HBASE-3071 added a script
to move regions off and on and to restart the server.  We could add a flag to the script that
invoked the full gc via JMX.
> Benoit has some trick for doing JMX w/o having to enable the JMX Mgt of JVM with java
options IIUC.

This message was sent by Atlassian JIRA

View raw message