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 76D7F112A6 for ; Wed, 4 Jun 2014 12:52:22 +0000 (UTC) Received: (qmail 26999 invoked by uid 500); 4 Jun 2014 12:52:20 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 26934 invoked by uid 500); 4 Jun 2014 12:52:20 -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 26923 invoked by uid 99); 4 Jun 2014 12:52:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jun 2014 12:52:20 +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 yuzhihong@gmail.com designates 209.85.160.49 as permitted sender) Received: from [209.85.160.49] (HELO mail-pb0-f49.google.com) (209.85.160.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jun 2014 12:52:17 +0000 Received: by mail-pb0-f49.google.com with SMTP id jt11so6952682pbb.36 for ; Wed, 04 Jun 2014 05:51:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=+3oNI6DB+AI3IEzvy+Gs7hPHOtPTDDKF9XlM4G3FXoU=; b=JTrT2vDWWF+q80LebSndjntP/0cXAMNe07noio6I2RmcbAUHzDeY1EB1CkhPRx5I/2 dY/HjQFFv7wzXgrceWUqUGHy0BV/Qe53kCi99y1HPm4R73Qs27mJvI0HV6gU1aTLrInT 5xm6kj84ONVa3wpMFRDaWV1Xlj3Dsus5kGD0qnsZZPu7lE1I4Mfl539MJW8SCfSdl+5+ G1NEiQk8jhGvzc7ZjZSCzGN5qKrruyKRfXqqe9QWz+O8bBYOVOBAqf9YtviiHZ+0oX8p lq48wtHUOQEZwF5gEDJnhaJCksaxDLHO74pl2dgRAKbxIBpQyJ94g8P6tWK3+BkieJSz lFnA== X-Received: by 10.68.213.74 with SMTP id nq10mr63424142pbc.4.1401886313035; Wed, 04 Jun 2014 05:51:53 -0700 (PDT) Received: from [192.168.0.13] (c-24-130-236-83.hsd1.ca.comcast.net. [24.130.236.83]) by mx.google.com with ESMTPSA id py7sm9738242pbb.78.2014.06.04.05.51.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Jun 2014 05:51:52 -0700 (PDT) References: <538F139E.6050305@viadeoteam.com> Mime-Version: 1.0 (1.0) In-Reply-To: <538F139E.6050305@viadeoteam.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <22C297D9-D7F5-4E69-B8A7-8C945A2A326D@gmail.com> Cc: user X-Mailer: iPhone Mail (10B146) From: Ted Yu Subject: Re: HBase export limit bandwith Date: Wed, 4 Jun 2014 05:51:52 -0700 To: "user@hbase.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org Can you use ExportSnapshot tool ? ExportSnapshot has option to limit bandwidth. See HBASE-11090. This feature is in the soon-to-be-released 0.98.3 See HBASE-11204 as well. Cheers On Jun 4, 2014, at 5:39 AM, Damien Hardy wrote: > Hello, > > We are trying to export HBase table on S3 for backup purpose. > By default export tool run a map per region and we want to limit output > bandwidth on internet (to amazon s3). > > We were thinking in adding some reducer to limit the number of writers > but this is explicitly hardcoded to 0 in Export class > ``` > // No reducers. Just write straight to output files. > job.setNumReduceTasks(0); > ``` > > Is there an other way (propertie?) in hadoop to limit output bandwidth ? > > -- > Damien >