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 1B52F19800 for ; Sat, 26 Mar 2016 15:43:22 +0000 (UTC) Received: (qmail 31519 invoked by uid 500); 26 Mar 2016 15:43:19 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 31443 invoked by uid 500); 26 Mar 2016 15:43:19 -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 31431 invoked by uid 99); 26 Mar 2016 15:43:19 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Mar 2016 15:43:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D35F6180225 for ; Sat, 26 Mar 2016 15:43:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id JExzCm0nUODK for ; Sat, 26 Mar 2016 15:43:16 +0000 (UTC) Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 63C805F3F0 for ; Sat, 26 Mar 2016 15:43:16 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id y6so6936112lbj.0 for ; Sat, 26 Mar 2016 08:43:16 -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; bh=Jmo8qxHJvpNLZmJNddR+BhAOot3Vr/atb3MOpk6XrgY=; b=F/KUnvfkHlv94LCJ9H3cWTb0wObs5Js8Lh1OUn2Ay1des9f+rkAleKUPtkcwZnwZcm K4NuV2bJjRT6hEda5YvTTEO+WetvK0eLVlNbXwGY/1TPxtyS1scGwLycUZGgVZJy8agI cnIJ7O0KrF3Xm74zFCiJ6gkei7XupQigHSrcjG64+XvUEmij1Zgja207RonT6XdQKLNC bZx/5bEzDeRZtNM9GOhpGD1aZNxLXrJNzHnBf2W80JIOXnT+s7pWGTW3uNT4uxbCgEsl bxM3eDOg2sH+6j4rniZdC9eOwXkrF1Vioa6GAWkejRdHZ8xjEjBjprE6Wd8+kJac+Wum FJfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=Jmo8qxHJvpNLZmJNddR+BhAOot3Vr/atb3MOpk6XrgY=; b=LA0+OePGIXyllZzsLRrpVhqIGRxkx/I7Np1BGgyYxqx5SveY1bNeLuWSCmn00xB0Xg 8jY9WKBcwpmbzwMGZTVtmcI1hZGRD8JLqVQhJQGe3YNAKXN+a6vbQNNgGwMSm2T4F896 K2yHOTlqQpeMXT+s+32JcNpAI0fjkbmbr6t/s5Fd6ZZct+V7/Euz9RzfPHOqn65HDrYz gCVFac4zlaKJNbC44higuxqZzmbL89AYc6Qar68Bv1Q6qD84/JzYLVyqLt5H1ffPIn0V 7SI5g+QXimUXAnJeCgSmQUAHEs7l72wl6X1miL4EVUP3eOteJDK/Z6149tLRV0YpQ9aK WmIA== X-Gm-Message-State: AD7BkJJgf1qe5o6ZPe3Gjg9tjUtewXcQfukSoiJg1OPxK+jTEUcedjnKI/Oj50g0dLs8AOh3xrYUaE4pESx9lA== MIME-Version: 1.0 X-Received: by 10.112.13.33 with SMTP id e1mr6035785lbc.79.1459006989326; Sat, 26 Mar 2016 08:43:09 -0700 (PDT) Received: by 10.114.200.112 with HTTP; Sat, 26 Mar 2016 08:43:09 -0700 (PDT) In-Reply-To: References: Date: Sat, 26 Mar 2016 16:43:09 +0100 Message-ID: Subject: Re: processing in coprocessor and region splitting From: =?UTF-8?B?RGFuaWVsIFBvxYJhY3phxYRza2k=?= To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a11c39e2652e038052ef589b1 --001a11c39e2652e038052ef589b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable unfortunately no Regards 2016-03-25 21:13 GMT+01:00 Ted Yu : > bq. calculating another new attributes of a trade > > Can you put the new attributes in separate columns ? > > Cheers > > On Fri, Mar 25, 2016 at 12:38 PM, Daniel Po=C5=82acza=C5=84ski < > dpolaczanski@gmail.com > > wrote: > > > The data is set of trades and the processing is some kind of enrichment > > (calculating another new attributes of a trade). All attributes are > needed > > (the original and new) > > > > 2016-03-25 18:41 GMT+01:00 Ted Yu : > > > > > bq. During the processing the size of the data is doubled. > > > > > > This explains the frequent split :-) > > > > > > Is the original data needed after post-processing (maybe for auditing= ) > ? > > > > > > Cheers > > > > > > On Fri, Mar 25, 2016 at 10:32 AM, Daniel Po=C5=82acza=C5=84ski < > > > dpolaczanski@gmail.com > > > > wrote: > > > > > > > I am testing different solutions (POC). > > > > The region size currenlty is 32MB (I know it should be >=3D 1GB, bu= t we > > are > > > > testing different solutions with smaller amount of the data ). So > > > > increasing region size is not a solution. Our problems can happen > even > > > when > > > > a region will be 1 GB. We want to proces the data with coprocessor > and > > > > hadoop map reduce. I can not have one big Region because I want > > sensible > > > > degree of paralerism (with Map Reduce and coprocessors). > > > > > > > > Increasing region size + pre-splitting is not an option as well > > because > > > I > > > > know nothing about keys(random long). > > > > > > > > During the processing the size of the data is doubled. > > > > > > > > And yes, coprocessor rewrites a lot of the data written into the > table. > > > The > > > > whole record is serialized to avro and stored in one column (storin= g > > > single > > > > attribute in single column we will try in the next POC) > > > > > > > > it is not a typical big data project where we can allow former > analysis > > > of > > > > the data:) > > > > > > > > 2016-03-25 17:38 GMT+01:00 Ted Yu : > > > > > > > > > What's the current region size you use ? > > > > > > > > > > bq. During the processing size of the data gets increased > > > > > > > > > > Can you give us some quantitative measure as to how much increase > you > > > > > observed (w.r.t. region size) ? > > > > > > > > > > bq. I was looking for some "global lock" in source code > > > > > > > > > > Probably not a good idea using global lock. > > > > > > > > > > I am curious, looks like your coprocesser may rewrite a lot of da= ta > > > > written > > > > > into the table. > > > > > Can client side accommodate such logic so that the rewrite is > > reduced ? > > > > > > > > > > Thanks > > > > > > > > > > On Fri, Mar 25, 2016 at 8:55 AM, Daniel Po=C5=82acza=C5=84ski < > > > > > dpolaczanski@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi, > > > > > > I have some processing in my coprocesserService which modifies > the > > > > > existing > > > > > > data in place. It iterates over every row, modifies and puts it > > back > > > to > > > > > > region. The table can be modified by only one client. > > > > > > > > > > > > During the processing size of the data gets increased -> region= 's > > > size > > > > > get > > > > > > increased -> region's split happens. It makes that the processi= ng > > is > > > > > > stopped by exception NotServingRegionException (because region = is > > > > closed > > > > > > and splited to two new regions so it is closed and doesn't exis= t > > > > > anymore). > > > > > > > > > > > > Is there any clean way to block Region's splitting? > > > > > > > > > > > > I was looking for some "global lock" in source code but I haven= 't > > > found > > > > > > anything helpfull. > > > > > > Another idea is to create custom RegionSplitPolicy and explicil= ty > > set > > > > > some > > > > > > Flag which will return false in shouldSplit(), but I'm not sure > yet > > > if > > > > it > > > > > > is safe. > > > > > > Could you advise? > > > > > > Regards > > > > > > > > > > > > > > > > > > > > > --001a11c39e2652e038052ef589b1--