Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 17 May 2012 04:31:04 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1561889221.7304.1337229064112.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <121259647.6610.1337212026520.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-6025) Expose Hadoop Dynamic Metrics
 through JSON Rest interface
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277545#comment-13277545 ] 

stack commented on HBASE-6025:
------------------------------

@Enis You saying that what comes out of jmx will show in a hadoop webapp servlet mounted at /jmx?  I did not know such a thing existed (I forgot hbase-5309).

I tried it.  Had to copy in jackson and newer hadoop (we ship 1.0.0 even in 0.94 which needs to be fixed).  I see /jmx metrics (We should add a 'metrics' link along the top beside the log level, thread dump, etc. servlets.

What other servlets are we missing out on @Enis?  There was a configuration dump IIRC but maybe thats not till 2.0.0 hadoop?

Oh, it looks like the jmx per-region stuff is showing under /jmx because Elliott already added this to 0.94 and trunk.

So, seems like, to make this work for trunk, all we have to do is:

1. update jackson and hadoop versions
2. Add a metrics link to show on all pages
3. Fix this exception:

{code}
2012-05-16 21:24:06,077 ERROR org.apache.hadoop.jmx.JMXJsonServlet: getting attribute CollectionUsageThresholdCount of java.lang:type=MemoryPool,name=Code Cache threw an exception
javax.management.RuntimeMBeanException: java.lang.UnsupportedOperationException: CollectionUsage threshold is not supported
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:856)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:869)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:670)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
	at org.apache.hadoop.jmx.JMXJsonServlet.writeAttribute(JMXJsonServlet.java:251)
	at org.apache.hadoop.jmx.JMXJsonServlet.listBeans(JMXJsonServlet.java:227)
	at org.apache.hadoop.jmx.JMXJsonServlet.doGet(JMXJsonServlet.java:159)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
	at org.apache.hadoop.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:835)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:326)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: java.lang.UnsupportedOperationException: CollectionUsage threshold is not supported
	at sun.management.MemoryPoolImpl.getCollectionUsageThresholdCount(MemoryPoolImpl.java:229)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
{code}

Should at least be backported to 0.94.

This is great.
                
> Expose Hadoop Dynamic Metrics through JSON Rest interface
> ---------------------------------------------------------
>
>                 Key: HBASE-6025
>                 URL: https://issues.apache.org/jira/browse/HBASE-6025
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira