Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3074DDBA7 for ; Wed, 6 Mar 2013 22:20:14 +0000 (UTC) Received: (qmail 62355 invoked by uid 500); 6 Mar 2013 22:20:14 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 62311 invoked by uid 500); 6 Mar 2013 22:20:14 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 62301 invoked by uid 99); 6 Mar 2013 22:20:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 22:20:13 +0000 Date: Wed, 6 Mar 2013 22:20:13 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-7721) Atomic multi-row mutations in META MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-7721: --------------------------------- Status: Open (was: Patch Available) > Atomic multi-row mutations in META > ---------------------------------- > > Key: HBASE-7721 > URL: https://issues.apache.org/jira/browse/HBASE-7721 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver > Reporter: Enis Soztutar > Assignee: Enis Soztutar > Fix For: 0.95.0, 0.98.0 > > Attachments: hbase-7721_v1.patch, hbase-7721_v2.patch, hbase-7721_v3.patch > > > Thanks to Lars' local transactions patch (HBASE-5229), we can entertain the possibility of doing local transactions within META regions. > We need this mainly for region splits and merges. Clients scan the META concurrent to the split/merge operations, and to prevent the clients from seeing overlapping region boundaries or holes in META, we just through hoops. For more backgroun, see BlockingMetaScannerVisitor, HBASE-5986, and my comments at https://reviews.apache.org/r/8716/. > Now, for the actual implementation options: > 1. As outlined in http://hadoop-hbase.blogspot.com/2012_02_01_archive.html, > - We have to implement a Custom RegionSplitPolicy for the META regions to ensure that a table's regions are always co-located in the same META region. Then we can add MultiRowMutationEndpoint as a system level coprocessor, and use it for META operations. > 2. Do smt like HBASE-7716, and expose local atomic multi-row operations as a native API. > 3. Move META to zookeeper. Use zookeeper.multi. > Then we can change region split / merge logic to make use of atomic META operations. > Thoughts, suggestions? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira