Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5439B90E5 for ; Thu, 5 Apr 2012 10:37:39 +0000 (UTC) Received: (qmail 27319 invoked by uid 500); 5 Apr 2012 10:37:37 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 27283 invoked by uid 500); 5 Apr 2012 10:37:37 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 27273 invoked by uid 99); 5 Apr 2012 10:37:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 10:37:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sdnetwork@gmail.com designates 74.125.82.41 as permitted sender) Received: from [74.125.82.41] (HELO mail-wg0-f41.google.com) (74.125.82.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 10:37:30 +0000 Received: by wgbds1 with SMTP id ds1so1292276wgb.2 for ; Thu, 05 Apr 2012 03:37:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=5C+Gnc4kOIvJUqtkYXt1cbEK5O0wsABGv9WBT3zeqjg=; b=dvt1HwCbY+TWNvYarSqyQb9Uy6TNorEIf4Gf6tinEjTSIbsx2+6fpTyGmQhvfh+9KC QVh2sjr0egR2Gt8y/AArHOwYZNz2C3/324HIwKJBBdcim8ChWffYT7h+7S7ovKppP+oO z1G/wOwcuyPk5vjr7/P9iYrpgEFPSniugQ4z4kVrropSbtgDxjxCtlBktVmunls1EyLf t5Yp8mszZjes6xmiSg4xu8h2/C/H7+4ahaHNk2yV8OK5qrAmjs/XXmIUJ6oxVsv4DQdJ jcywt/hnTvpzchKrdWO+0EoqUkesrNjenJQCkJX6COpdX9LPVKm9k/42DLXoHvJlFfpE GXXg== MIME-Version: 1.0 Received: by 10.216.132.229 with SMTP id o79mr1336388wei.64.1333622230688; Thu, 05 Apr 2012 03:37:10 -0700 (PDT) Received: by 10.223.102.195 with HTTP; Thu, 5 Apr 2012 03:37:10 -0700 (PDT) In-Reply-To: References: Date: Thu, 5 Apr 2012 12:37:10 +0200 Message-ID: Subject: Re: hbase map/reduce questions From: Arnaud Le-roy To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable but do you think that i can change the default behavior ? for exemple i have ten nodes in my cluster and my table is stored only on two nodes this table have 1000 rows. with the default behavior only two nodes will work for a map/reduce task., isn't it ? if i do a custom input that split the table by 100 rows, can i distribute manually each part on a node regardless where the data is ? Le 5 avril 2012 00:36, Doug Meil a =E9crit = : > > The default behavior is that the input splits are where the data is store= d. > > > > > On 4/4/12 5:24 PM, "sdnetwork" wrote: > >>ok thanks, >> >>but i don't find the information that tell me how the result of the split >>is >>distrubuted across the different node of the cluster ? >> >>1) randomely ? >>2) where the data is stored ? >> >> >> >> >> > >