Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4878E18176 for ; Fri, 9 Oct 2015 17:54:06 +0000 (UTC) Received: (qmail 11548 invoked by uid 500); 9 Oct 2015 17:54:06 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 11301 invoked by uid 500); 9 Oct 2015 17:54:06 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 11013 invoked by uid 99); 9 Oct 2015 17:54:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Oct 2015 17:54:05 +0000 Date: Fri, 9 Oct 2015 17:54:05 +0000 (UTC) From: "marco polo (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-4023) Table Ops appear to lock namespace and block other table ops 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/ACCUMULO-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950864#comment-14950864 ] marco polo commented on ACCUMULO-4023: -------------------------------------- Thanks for testing. I'll create another ticket when I've tracked down a better why. I know the symptoms but not the problem. I didn't inspect the code very well as I told you, but I've found a new condition where I can run two delete rows in a row and see the same wait and problem. I'm leaning toward fate op problems...but I will open another ticket when I find the problem. Thanks again. > Table Ops appear to lock namespace and block other table ops > ------------------------------------------------------------ > > Key: ACCUMULO-4023 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4023 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.6.4 > Reporter: marco polo > Priority: Critical > > I've noticed table repeatable operations impacting other table ops. Upon looking at the code it appears as though we reserve the name space, attempt to lock it, and then lock the table. Someone more familiar with the code can debunk me, but it appears as though we're blocking table ops on alternate tables. The same code for getting the lock is used for namespace and tables, it seems as though in most cases we only want a table lock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)