hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harsh J <ha...@cloudera.com>
Subject Re: System.out.printlin vs Counters
Date Wed, 27 Mar 2013 10:27:46 GMT
I do not understand 1 and 2: Counters are used to count things in the MR
framework in a distributed manner and get aggregate at the JobTracker
level; System.out is merely used to write to STDOUT. Why are you
comparing the two?

3: The limit means the total number of counter names accepted from a
single job. Your example would create one such new counter called
TestGroup1.TestName1. You could also increment TestName2, etc.… but
only up to a global max of 120 of such new counters.

On Wed, Mar 27, 2013 at 3:51 PM, Sai Sai <saigraph@yahoo.in> wrote:
> Q1. Is it right to assume the System.out.println statements are used only in
> eclipse environment and
> In a multi node cluster environment we need to use counters.
> Q2. I am slightly confused as it appears like using System.out.println
> statements
> we r able to get detailed info at every line of code in eclipse and counters
> just give few lines and not as detailed as System.out.println statements do
> so what should we do in a multi node cluster enivronment.
> Q3. Also when they say the limit of counters is 120 does that mean that in
> the output if we use:
> context.getCounters("TestGroup1","TestName1").increment(1);
> more than 120 times it will not print it. or does it refer to 120 options of
> counters in an enum that we can define.
> Any help is really appreciated.
> Thanks
> Sai

Harsh J

View raw message