Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <14169268.56641273878344771.JavaMail.jira@thor>
Date: Fri, 14 May 2010 19:05:44 -0400 (EDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1779) Should we provide a way to know
 JobTracker's memory info from client?
In-Reply-To: <24786588.59671273468188564.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867729#action_12867729 ] 

dhruba borthakur commented on MAPREDUCE-1779:
---------------------------------------------

I am fine moving it to 0.22.

> Should we provide a way to know JobTracker's memory info from client?
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1779
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1779
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client, jobtracker
>    Affects Versions: 0.21.0
>            Reporter: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.21.0
>
>
> In HADOOP-4435, in branch 0.20, getClusterStatus() method returns JobTracker's used memory and total memory.
> But these details are missed in new api (through MAPREDUCE-777).
> If these details are needed only for web UI, I don't think they are needed for client.
> So, should we provide a way to know JobTracker's memory info from client?
> If yes, an api should be added in org.apache.hadoop.mapreduce.Cluster for the same.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.