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 E22991138D for ; Thu, 24 Apr 2014 16:17:30 +0000 (UTC) Received: (qmail 50337 invoked by uid 500); 24 Apr 2014 16:17:27 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 50278 invoked by uid 500); 24 Apr 2014 16:17:27 -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 50270 invoked by uid 99); 24 Apr 2014 16:17:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 16:17:27 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of scott.kuehn@opower.com designates 209.85.216.172 as permitted sender) Received: from [209.85.216.172] (HELO mail-qc0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 16:17:21 +0000 Received: by mail-qc0-f172.google.com with SMTP id i8so2779713qcq.3 for ; Thu, 24 Apr 2014 09:17:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=eyg72q8QKjY3aD8wHM4N3yMTfz25prabqb1mDAkx8Ac=; b=GFmJcrmCHlJKmVmHbiP+VBRovS6omTvrRPnTEvecwCBVsVyrwHCRbcwGBzRJVe4Gxm i0H8BddT0gG1lxT1tx7/ENBz8fPtPTmtJ34pjLSryTr5MHj2+aDdCAKnbwSBY6aYL2AQ KrRiOb6iOyKuCRRL1/LxZ0Y1Y3vsjvQk3kteulfEA9orFKC/q3MkwmpzK+XD5vk+95O7 BIFkg4mllPh5+42WIw+rOVXqO8XnYogcgviWwj55N1CBEzuDwAZW+De24q7WvrJM3PBA CsjFULG54HKvB+QDJIOlMgRunND01B6duYbErFSGohdpLpJj5HRmIVW7Ig9LA8N3UQjb BAmg== X-Gm-Message-State: ALoCoQlK4cdRRDVxJnMqeD1DuD3EUiNJnPTYwc9gsvoTgHVwFlmEzhY/EDF3hRYlUJaBZTNdGN+X MIME-Version: 1.0 X-Received: by 10.229.176.72 with SMTP id bd8mr4231331qcb.12.1398356220765; Thu, 24 Apr 2014 09:17:00 -0700 (PDT) Received: by 10.140.48.175 with HTTP; Thu, 24 Apr 2014 09:17:00 -0700 (PDT) Date: Thu, 24 Apr 2014 09:17:00 -0700 Message-ID: Subject: Options for limiting bandwidth in ExportSnapshot From: Scott Kuehn To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a11c303eccf1d1604f7cc2d15 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c303eccf1d1604f7cc2d15 Content-Type: text/plain; charset=ISO-8859-1 Any recommendations on how to limit the bandwidth consumption of an ExportSnapshot job? I'd like to control bandwidth consumption so important network workloads, like shuffling and balancing, are reserved some bandwidth while a lower-priority ExportSnapshot job is running. Note that distcp jobs provide the ability to limit bandwidth by exposing the num-mappers and bandwidth options. I'm looking to achieve something similar with ExportSnapshot. ExportSnapshot ref (bottom of page): http://hbase.apache.org/book/ops.snapshots.html --001a11c303eccf1d1604f7cc2d15--