Return-Path: 
 <hdfs-issues-return-17830-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-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 E1A46839
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Sun,  1 May 2011 04:27:43 +0000 (UTC)
Received: (qmail 94584 invoked by uid 500); 1 May 2011 04:27:43 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 94492 invoked by uid 500); 1 May 2011 04:27:42 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 94483 invoked by uid 99); 1 May 2011 04:27:42 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 May 2011 04:27:42 +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; Sun, 01 May 2011 04:27:41 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 2364BBB92D
	for <hdfs-issues@hadoop.apache.org>; Sun,  1 May 2011 04:27:03 +0000 (UTC)
Date: Sun, 1 May 2011 04:27:03 +0000 (UTC)
From: "Tanping Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <2022975446.14002.1304224023141.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1690833796.13999.1304223783797.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-1874) Programmatically start hdfs processes
 with JMX port open
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Tanping Wang updated HDFS-1874:
-------------------------------

    Attachment: HDFS-1874.patch

Change GetConf to enable
$bin/hdfs getconf -nameNodeJmxPort
in order to grab namenode jmx port from hdfs-site.xml property.  The new property introduced to hdfs-site.xml is

   <property>
   <name>dfs.namenode.jmxport</name>
     <value>8004</value>
     <description>namenode jmxport </description>
   </property>


> Programmatically start hdfs processes with JMX port open 
> ---------------------------------------------------------
>
>                 Key: HDFS-1874
>                 URL: https://issues.apache.org/jira/browse/HDFS-1874
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: data-node, name-node
>    Affects Versions: 0.23.0
>            Reporter: Tanping Wang
>            Assignee: Tanping Wang
>            Priority: Minor
>             Fix For: 0.23.0
>
>         Attachments: HDFS-1874.patch
>
>
> Federation web console makes JMX calls to each name node in order to collect statistics from the name nodes.  This requires name node processes to have JMX port open for communication.  We propose a programmatic way to start name node processes with JMX enabled.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira