Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 77365 invoked from network); 24 Jul 2009 10:30:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Jul 2009 10:30:02 -0000 Received: (qmail 29443 invoked by uid 500); 24 Jul 2009 10:31:06 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 29389 invoked by uid 500); 24 Jul 2009 10:31:06 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 29379 invoked by uid 99); 24 Jul 2009 10:31:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2009 10:31:06 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hbase.user.ninad@gmail.com designates 209.85.221.188 as permitted sender) Received: from [209.85.221.188] (HELO mail-qy0-f188.google.com) (209.85.221.188) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2009 10:30:57 +0000 Received: by qyk26 with SMTP id 26so1979229qyk.5 for ; Fri, 24 Jul 2009 03:30:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=0JMhW2+EckDqpi3umto7MmktUmDhKgjFfDsvVnRn6/g=; b=VsGbTNTRwQ5/bmxiWw3PCmPSVcnSxajQLROjLYI25SUsizNU2yRHqiSN2Oj0YebNst vS8JzvXLqbEtcsc2AZfwIu/b4WEZQs9O2AisCSP/8Cdo7DvXS+k0SpZHi21NBC50SWgC A3UF/veUv9+8aRIbvCvp8PpG0rn+StO/goIgw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=FXuru+Ng3Swapavht7SJ0ED0mTqWPfQ74mibDulSbtobg7/oRBZ0vlXq1+oAEmUW8E jOaGiuiZ1cY2KnvwQZZshBawClu4g2x+3Q9m6OsBeGipYAETVNd3UhB7hIYJETLncHIc dzVBq5s1283IjmNTDy2O0N8pPvccZegFY4N2w= MIME-Version: 1.0 Received: by 10.220.94.69 with SMTP id y5mr2119893vcm.6.1248431435011; Fri, 24 Jul 2009 03:30:35 -0700 (PDT) In-Reply-To: <24636315.post@talk.nabble.com> References: <24636315.post@talk.nabble.com> Date: Fri, 24 Jul 2009 16:00:34 +0530 Message-ID: <4d371b590907240330r39d4b1d3w946e18810204dcb3@mail.gmail.com> Subject: Re: Why only few map tasks are running at a time inspite of plenty of scope for remaining? From: Ninad Raut To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016363b938035d8c3046f7118e0 X-Virus-Checked: Checked by ClamAV on apache.org --0016363b938035d8c3046f7118e0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit If your data is stored just on one regionserver you will have only one map inspite of setting conf.set("mapred.tasktracker.map.tasks.maximum", "2"); there are two approaches: On Fri, Jul 24, 2009 at 4:54 AM, akhil1988 wrote: > > Hi all, > > I am using a HTable as input to my map jobs and my reducer outputs to > another Htable. There are 10 regions of my input HTable. And I have set > conf.set("mapred.tasktracker.map.tasks.maximum", "2"); > conf.set("mapred.tasktracker.map.tasks.maximum", "2"); > c.setNumReduceTasks(26); > My cluster contains 15 nodes(out of which 2 are maters). When I run my job, > only 2 map tasks run at a time and the remaining 8 are shown as pending. 24 > reduce tasks(out of 26) also get started initially and remaing 2 are shown > as pending. I am confused why only 2 tasks are running at a time, though > there are a total of 26 slots for map tasks. > > However, this does not happen when I run jobs in which I take files as > inputs(i.e. only simple MapReduce jobs and not involving HBase at all). > Only > when a Htable is taken as input very few map tasks run concurrently than > expected. > > Can anyone suggest why this is happening? > > What I have observed in simple mapreduce jobs that first all map tasks are > instantiated and then reduce tasks. But this does not seem to be happening > in HTable case?? > > -- > View this message in context: > http://www.nabble.com/Why-only-few-map-tasks-are-running-at-a-time-inspite-of-plenty-of-scope-for-remaining--tp24636315p24636315.html > Sent from the HBase User mailing list archive at Nabble.com. > > --0016363b938035d8c3046f7118e0--