On Sat, Jan 22, 2011 at 9:59 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
> In the test code, JobTracker is returned from:
> mr = new MiniMRCluster(0, 0, 0, "file:///", 1, null, null, null,
> jobTracker = mr.getJobTrackerRunner().getJobTracker();
> I guess it is not exposed in non-test code.
> On Sat, Jan 22, 2011 at 6:38 PM, Zhenhua Guo <[EMAIL PROTECTED]> wrote:
>> How to get JobTracker object?
>> On Sun, Jan 23, 2011 at 5:46 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
>> > You can use the following code:
>> > JobClient jc = new JobClient(jobConf);
>> > int numReduces = jc.getClusterStatus().getMaxReduceTasks();
>> > For 0.20.3, you can use:
>> > ClusterMetrics metrics = jobTracker.getClusterMetrics();
>> > On Sat, Jan 22, 2011 at 9:57 AM, Zhenhua Guo <[EMAIL PROTECTED]> wrote:
>> >> I want to get metrics information (e.g. number of Maps, number of
>> >> Reduces, memory use, load) by APIs. I found two useful classes -
>> >> ClusterStatus and ClusterMetrics. My question is how I can get
>> >> instances of that two classes? From JobClient or JobTracker? Any
>> >> suggested alternative way to get the information?
>> >> Thanks
>> >> Gerald
Correct JobTracker is the JobTracker itself that does not have any interface.
However using JobClient you can mine most of the information out from
the Job Tracker.
My cacti graphing package takes that exact approach to pull
information that is not a JMXCounter such as.