Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 92628 invoked from network); 5 Jan 2009 20:25:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Jan 2009 20:25:04 -0000 Received: (qmail 13541 invoked by uid 500); 5 Jan 2009 20:24:58 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 13487 invoked by uid 500); 5 Jan 2009 20:24:58 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 13476 invoked by uid 99); 5 Jan 2009 20:24:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jan 2009 12:24:58 -0800 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.218.16] (HELO mail-bw0-f16.google.com) (209.85.218.16) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jan 2009 20:24:50 +0000 Received: by bwz9 with SMTP id 9so19036119bwz.5 for ; Mon, 05 Jan 2009 12:24:29 -0800 (PST) Received: by 10.103.182.3 with SMTP id j3mr7503242mup.113.1231187069512; Mon, 05 Jan 2009 12:24:29 -0800 (PST) Received: by 10.103.107.16 with HTTP; Mon, 5 Jan 2009 12:24:28 -0800 (PST) Message-ID: Date: Mon, 5 Jan 2009 12:24:28 -0800 From: "Aaron Kimball" To: core-user@hadoop.apache.org, saptarshi.guha@gmail.com Subject: Re: Map input records(on JobTracker website) increasing and decreasing In-Reply-To: <1e7471d50901050834t37e687f1t8df29d7e974aee09@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_208610_6431267.1231187069442" References: <1e7471d50901050834t37e687f1t8df29d7e974aee09@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_208610_6431267.1231187069442 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline The actual number of input records is most likely steadily increasing. The counters on the web site are inaccurate until the job is complete; their values will fluctuate wildly. I'm not sure why this is. - Aaron On Mon, Jan 5, 2009 at 8:34 AM, Saptarshi Guha wrote: > Hello, > When I check the job tracker web page, and look at the Map Input > records read,the map input records goes up to say 1.4MN and then drops > to 410K and then goes up again. > The same happens with input/output bytes and output records. > > Why is this? Is there something wrong with the mapper code? In my map > function, i assume I have received one line of input. > The oscillatory behavior does not occur for tiny datasets, but for 1GB > of data (tiny for others) i see this happening. > > Thank s > Saptarshi > -- > Saptarshi Guha - saptarshi.guha@gmail.com > ------=_Part_208610_6431267.1231187069442--