Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7067A4F37 for ; Fri, 17 Jun 2011 20:18:32 +0000 (UTC) Received: (qmail 37412 invoked by uid 500); 17 Jun 2011 20:18:32 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 37376 invoked by uid 500); 17 Jun 2011 20:18:32 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 37368 invoked by uid 99); 17 Jun 2011 20:18:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2011 20:18:32 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2011 20:18:29 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id AECFF41E377 for ; Fri, 17 Jun 2011 20:17:48 +0000 (UTC) Date: Fri, 17 Jun 2011 20:17:48 +0000 (UTC) From: "Owen O'Malley (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1664707300.16307.1308341868711.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1728703995.16605.1297739397760.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (HADOOP-7144) Expose JMX with something like JMXProxyServlet MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley updated HADOOP-7144: ---------------------------------- Fix Version/s: (was: 0.20.205.0) > Expose JMX with something like JMXProxyServlet > ----------------------------------------------- > > Key: HADOOP-7144 > URL: https://issues.apache.org/jira/browse/HADOOP-7144 > Project: Hadoop Common > Issue Type: New Feature > Reporter: Luke Lu > Assignee: Robert Joseph Evans > Labels: jmx > Fix For: 0.20.204.0, 0.23.0 > > Attachments: HADOOP-7411-0.20.20X-V1.patch, HADOOP-7411-0.20.20X-V2.patch, HADOOP-7411-trunk-V1.patch, HADOOP-7411-trunk-V2.patch, HADOOP-7411-trunk-alpha.patch, jmx.json > > > Much of the Hadoop metrics and status info is available via JMX, especially since 0.20.100, and 0.22+ (HDFS-1318, HADOOP-6728 etc.) For operations staff not familiar JMX setup, especially JMX with SSL and firewall tunnelling, the usage can be daunting. Using a JMXProxyServlet (a la Tomcat) to translate JMX attributes into JSON output would make a lot of non-Java admins happy. > We could probably use Tomcat's JMXProxyServlet code directly, if it's already output some standard format (JSON or XML etc.) The code is simple enough to port over and can probably integrate with the common HttpServer as one of the default servelet (maybe /jmx) for the pluggable security. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira