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 EBAE51853E for ; Thu, 11 Jun 2015 03:17:18 +0000 (UTC) Received: (qmail 25679 invoked by uid 500); 11 Jun 2015 03:17:17 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 25608 invoked by uid 500); 11 Jun 2015 03:17:17 -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 25596 invoked by uid 99); 11 Jun 2015 03:17:16 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jun 2015 03:17:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 4E279C0940 for ; Thu, 11 Jun 2015 03:17:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.792 X-Spam-Level: * X-Spam-Status: No, score=1.792 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-1.108, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Xjrj0ybSPurM for ; Thu, 11 Jun 2015 03:17:10 +0000 (UTC) Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com [209.85.220.171]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 07FBA27621 for ; Thu, 11 Jun 2015 03:17:10 +0000 (UTC) Received: by qkx62 with SMTP id 62so34673332qkx.3 for ; Wed, 10 Jun 2015 20:17:09 -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; bh=joraqgY4RifxcbR/ZBV0wCzAIwhRiiea8bfy1BRyenk=; b=eGgL8jl3XNceD24TjRWWJabpviD22K6Ft4oGSqHWsm8SKO0djBV4vRgYKWJBl6nriM mePkG7FH35HBePXhMrCwOw5pSNgHBlU3n7KVwO2PfY6dhu0GGPnX9nnBWt2Z/hLBw89N 0nLB/iUg3AgY+7sYDUKArqUQzyRk8ZzTGTUgNQ3VN+uqvNCInnwLktwKzEA3REMMeG/C GIwlWbN+XFvHI5epRNEIF900HmoTU/D32P+6PeBcvQ5yCS0Zd4RGmL7GRVxp0laFEyDB N3Plak7CgKzEjSf6BTP7wKPcc37h5quCEfSC+5DbjmtinCtOAQQdBVNW1oMssLG2EtgG a68w== MIME-Version: 1.0 X-Received: by 10.55.33.40 with SMTP id h40mr13888556qkh.69.1433992629224; Wed, 10 Jun 2015 20:17:09 -0700 (PDT) Received: by 10.140.83.199 with HTTP; Wed, 10 Jun 2015 20:17:09 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Jun 2015 20:17:09 -0700 Message-ID: Subject: Re: How to monitor and control heavy network traffic for region server From: Vladimir Rodionov To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a1140690c4688e30518356dc7 --001a1140690c4688e30518356dc7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Louis, What do you mean by "monitor the long scan"? If you need to throttle network IO during scan, you have to do it on a client side. Take a look at org.apache.hadoop.hbase.io.hadoopbackport.ThrottledInputStream as an example, something similar you will need to implement on top of ResultScanner - ThrottledResultScanner. Good idea for improvement, actually. -Vlad On Wed, Jun 10, 2015 at 7:30 PM, Louis Hust wrote: > hi, Dave, > > For now we will not upgrade the version, so if there is something we can > monitor the long scan for 0.96? > > 2015-06-11 2:00 GMT+08:00 Dave Latham : > > > I'm not aware of anything in version 0.96 that will limit the scan for > > you - you may have to do it in your client yourself. If you're > > willing to upgrade, do check out the throttling available in HBase > > 1.1: > > > https://blogs.apache.org/hbase/entry/the_hbase_request_throttling_feature > > > > > > > > On Wed, Jun 10, 2015 at 4:15 AM, =E5=A8=84=E5=B8=85 wrote: > > > any ideas? > > > > > > 2015-06-10 16:01 GMT+08:00 =E5=A8=84=E5=B8=85 : > > > > > >> Hi all, > > >> > > >> We are using HBASE 0.96 with Hadoop 2.2.0, recently we found there a= re > > some > > >> SCAN operations last for more than 1 hours, which lead to heavy > network > > >> traffic, because some data is not > > >> stored at local data node and the region is very big, about 100G-500= G=E3=80=82 > > >> > > >> With heavy network traffic, the region server then can not offer > service > > >> cause the NIC is full. > > >> > > >> From DBA view point, I want to know if there is some operation for > HBase > > >> to limit the large scan or if there is some flow control for SCAN > > operation > > >> and how can we monitor the long SCAN operation=E3=80=82 > > >> > > > --001a1140690c4688e30518356dc7--