Return-Path: 
 <common-user-return-17739-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-common-user-archive@www.apache.org
Received: (qmail 52698 invoked from network); 29 Sep 2009 06:56:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 29 Sep 2009 06:56:05 -0000
Received: (qmail 7378 invoked by uid 500); 29 Sep 2009 06:56:00 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 7260 invoked by uid 500); 29 Sep 2009 06:56:00 -0000
Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-user@hadoop.apache.org>
List-Id: <common-user.hadoop.apache.org>
Reply-To: common-user@hadoop.apache.org
Delivered-To: mailing list common-user@hadoop.apache.org
Received: (qmail 7238 invoked by uid 99); 29 Sep 2009 06:56:00 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2009 06:56:00 +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 (nike.apache.org: domain of cpbhagtani@gmail.com designates
 209.85.222.195 as permitted sender)
Received: from [209.85.222.195] (HELO mail-pz0-f195.google.com)
 (209.85.222.195)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2009 06:55:51 +0000
Received: by pzk33 with SMTP id 33so25072pzk.2
        for <multiple recipients>; Mon, 28 Sep 2009 23:55:29 -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:cc:content-type;
        bh=fi8ntBGXBUanbyTaDjTCfKs+jKNyRFuMtr9r/HQjqRg=;
        b=pnz3RR4x3ygwyYuDQ2PQ/TkzLO/jueH1XnnerlwpBnF+svhCAjf3JqTIc0cv4KofDg
         sTNtBSwzbWNZx5t/Jk1yn9MS9HSQZJzXfrIS/v39pPnlJNUaicZTTVwWvMnwaG+vuUXv
         ZjfA69WJE7t+7CmvAtg9wvoqgYToUL0C8BQrw=
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
         :cc:content-type;
        b=UVTxCAehXplE65dqwlrF3yO9ZvkaHQayfRJu0hCI6/y2ByS+adnjEobR9mkwScVZcT
         LN6B+W8yy2+99p9oc6OIVieRTw7HyI+xsMxnCcmcCOUIncxw52lC/CO4dk+oMjO3gliS
         Lb5JS0FPpbLVNbLfmrTK/vS/MOV4hTHLzgp7Q=
MIME-Version: 1.0
Received: by 10.142.1.29 with SMTP id 29mr277624wfa.79.1254207329784; Mon, 28
	Sep 2009 23:55:29 -0700 (PDT)
In-Reply-To: <445c748b0909251748n3d949dach257da8283ca22091@mail.gmail.com>
References: <445c748b0909251748n3d949dach257da8283ca22091@mail.gmail.com>
Date: Tue, 29 Sep 2009 12:25:29 +0530
Message-ID: <4061df20909282355v3ce75646qfdf480952e4a6176@mail.gmail.com>
Subject: Re: Best Idea to deal with following situation
From: Chandraprakash Bhagtani <cpbhagtani@gmail.com>
To: common-user@hadoop.apache.org
Cc: core-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=00504502b23a5dd30c0474b1e66d
X-Virus-Checked: Checked by ClamAV on apache.org

--00504502b23a5dd30c0474b1e66d
Content-Type: text/plain; charset=ISO-8859-1

you can write your custom partitioner instead of hash partitioner

On Sat, Sep 26, 2009 at 6:18 AM, Pankil Doshi <forpankil@gmail.com> wrote:

> Hello everyone,
>
> I have job whose result has  only 5 keys but but each key has long list of
> values like in 100000's .
> What should be best way to deal with it. I feel few of my reducers get over
> loaded as two or more keys go to same reduce and hence they have lots of
> work to do.
>
> So what should be best way out with this situation?
>
> Pankil
>



-- 
Thanks & Regards,
Chandra Prakash Bhagtani,

--00504502b23a5dd30c0474b1e66d--