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 0B2C318E8C for ; Fri, 25 Mar 2016 15:56:04 +0000 (UTC) Received: (qmail 24796 invoked by uid 500); 25 Mar 2016 15:56:02 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 24725 invoked by uid 500); 25 Mar 2016 15:56:02 -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 24713 invoked by uid 99); 25 Mar 2016 15:56:01 -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; Fri, 25 Mar 2016 15:56:01 +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 2627118021C for ; Fri, 25 Mar 2016 15:56:01 +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-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id oBzYI_AsfaOy for ; Fri, 25 Mar 2016 15:55:59 +0000 (UTC) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 73FA75FAE3 for ; Fri, 25 Mar 2016 15:55:58 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id bc4so50402993lbc.2 for ; Fri, 25 Mar 2016 08:55:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=Fnq7jtRWopC9mNVi5RcDUfmtaPZmZPmBM9TUccbxtbw=; b=jv2q4y/jAK4EmWv8IGMl+uYPO0KwR0DaPszReidMI95V5OXLYaP4BdtF/SMXSxjDJJ TjNtRKurq9kvKqPCGBt5aFAdysJCjEnjGyKj5HcrTDLwAOpPL1W+2g24GPWmOYZUpenv zdTFqhFrw1U44ystfijr+shS++cRCXqqgX0OUu/EFDe5ay1+qYs4/E9X0BHcJzB9/iGD A5hLI+Ukd59izNvbgcAX99lQJC4FZD/s564eJnbqhomHfgpXZdC51QyBlM+OBzv8duQe RlRgT99BaSPsiP+C4uV7oNXl/mT5WoqUvYLi5xfER9y8uY3jRHbbN9LgdS/d1BpRKrOP QMSw== 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; bh=Fnq7jtRWopC9mNVi5RcDUfmtaPZmZPmBM9TUccbxtbw=; b=SxjRQUeujfbUixSYF0qkSFPcCOdehqDFkUqXZM0U5eUwMHQTOrTrA19ZPX/A0vugJR 2qSH6mfGUpBHgohRThnqXHc+0Tw+jaW/hvZ6rPuRZbmSp7BLXC0dMu7NWoBujBqahnz1 gaS9kLq4bleBt6KPDnvy+XwNhXnbFnXqaHCx4rxVlm304SLOVH1UfVA4ZljsPDmBFi9y h/saBi571zLdy2x9EVy0isCGnH33P0vaNuEdIjYb1HsPg/mhgKmerqj821Kb+yQA6Ati kBCXSugaCNAsm/Jd5WznN5ePxUjB9Umpl/0+PRslcmJeGjMotIAB5EoEgYtH+/fiGL0q /1oQ== X-Gm-Message-State: AD7BkJKkwE43VERvp5Y7QCHnm4hZbMjHxYETDDxyDrdW3jZDuCPGhzyUWRmOLYw8rJ9H8PI9Cw5M1yt0pwcp6g== MIME-Version: 1.0 X-Received: by 10.112.201.202 with SMTP id kc10mr6010578lbc.33.1458921351883; Fri, 25 Mar 2016 08:55:51 -0700 (PDT) Received: by 10.114.200.112 with HTTP; Fri, 25 Mar 2016 08:55:51 -0700 (PDT) Date: Fri, 25 Mar 2016 16:55:51 +0100 Message-ID: Subject: processing in coprocessor and region splitting From: =?UTF-8?B?RGFuaWVsIFBvxYJhY3phxYRza2k=?= To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a11c26b22ef37c7052ee1981e --001a11c26b22ef37c7052ee1981e Content-Type: text/plain; charset=UTF-8 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 processing is stopped by exception NotServingRegionException (because region is closed and splited to two new regions so it is closed and doesn't exist 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 explicilty set some Flag which will return false in shouldSplit(), but I'm not sure yet if it is safe. Could you advise? Regards --001a11c26b22ef37c7052ee1981e--