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 A3F3AF7EF for ; Fri, 5 Jul 2013 15:29:52 +0000 (UTC) Received: (qmail 85165 invoked by uid 500); 5 Jul 2013 15:29:50 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 84999 invoked by uid 500); 5 Jul 2013 15:29:49 -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 84967 invoked by uid 99); 5 Jul 2013 15:29:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jul 2013 15:29:48 +0000 Date: Fri, 5 Jul 2013 15:29:48 +0000 (UTC) From: "Dave Latham (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-8877) Reentrant row locks MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Dave Latham created HBASE-8877: ---------------------------------- Summary: Reentrant row locks Key: HBASE-8877 URL: https://issues.apache.org/jira/browse/HBASE-8877 Project: HBase Issue Type: Bug Components: Coprocessors, regionserver Reporter: Dave Latham Assignee: Dave Latham Fix For: 0.95.2 HBASE-8806 revealed performance problems with batch mutations failing to reacquire the same row locks. It looks like HBASE-8806 will use a less intrusive change for 0.94 to have batch mutations track their own row locks and not attempt to reacquire them. Another approach will be to support reentrant row locks directly. This allows simplifying a great deal of calling code to no longer track and pass around lock ids. One affect this change will have is changing the RegionObserver coprocessor's methods preBatchMutate and postBatchMutate from taking a {{MiniBatchOperationInProgress> miniBatchOp}} to taking a {{MiniBatchOperationInProgress miniBatchOp}}. I don't believe CPs should be relying on these lock ids, but that's a potential incompatibility. -- 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