Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A0A9118E3D for ; Tue, 5 Jan 2016 22:55:57 +0000 (UTC) Received: (qmail 42986 invoked by uid 500); 5 Jan 2016 22:55:57 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 42890 invoked by uid 500); 5 Jan 2016 22:55:57 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 42878 invoked by uid 99); 5 Jan 2016 22:55:56 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jan 2016 22:55:56 +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 1AC621804DD for ; Tue, 5 Jan 2016 22:55:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.898 X-Spam-Level: ** X-Spam-Status: No, score=2.898 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=-0.001, 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 mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Oiyh0TjIJ7VE for ; Tue, 5 Jan 2016 22:55:55 +0000 (UTC) Received: from mail-yk0-f171.google.com (mail-yk0-f171.google.com [209.85.160.171]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 92FF631A9A for ; Tue, 5 Jan 2016 22:55:54 +0000 (UTC) Received: by mail-yk0-f171.google.com with SMTP id x67so298039810ykd.2 for ; Tue, 05 Jan 2016 14:55:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=/dJ8SbXu8O3JH5ogVM+pXtCc0R7bKzYoBd15Q8e/vCw=; b=0mx0NJUOZsnyo4Qg+pTvU62Fxf+AlG/fojBHLhMY2o2bb9LndJokIFnD/ScRz9/Tkz zTfuMfLLDBS/9p2HqOG2r8x0h8ehROMnRVfBMW3hh/1OOSqyQSZTQuAHOX9i9N8uTPZg eGq7UM2jj2hUnTrHmwE8izvg+0giuzlX/SNvfwIXNGjXEtIhQIDe8BXWfsyG7nDZ1xNE pK0Ln4zYEPf+5aIFYw6bgj3w18xAeICJ+5bs9FG0/fHbYhRPtOmNeShbk56Ij+Ju0aFu X2RjKcVM0HubIMVX5GfJ1XeAWFXCCoiHGQbkj8YNZs4H2v9mJovBVlXuE6QZwVquvpFM KW1w== MIME-Version: 1.0 X-Received: by 10.13.218.68 with SMTP id c65mr72046981ywe.315.1452034553569; Tue, 05 Jan 2016 14:55:53 -0800 (PST) Received: by 10.37.207.5 with HTTP; Tue, 5 Jan 2016 14:55:53 -0800 (PST) Date: Tue, 5 Jan 2016 14:55:53 -0800 Message-ID: Subject: identifying source of region split request From: Ted Yu To: "dev@hbase.apache.org" Content-Type: multipart/alternative; boundary=94eb2c07eaa0c46c8005289e23d7 --94eb2c07eaa0c46c8005289e23d7 Content-Type: text/plain; charset=UTF-8 Hi, I recently worked on improving region normalization feature. If region split request triggered by the execution of SplitNormalizationPlan fails, there is no way of knowing whether the failed split originated from region normalization. Such association would give RegionNormalizer information so that it can make better normalization decisions in the subsequent invocations. One enhancement I can think of is to embed metadata in SplitRequest which gets passed through RegionStateTransitionContext when RegionServerServices#reportRegionStateTransition() is called. This way, RegionStateListener can be notified with the metadata (id of the requester). Comment is welcome. --94eb2c07eaa0c46c8005289e23d7--