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 9230318F33 for ; Fri, 9 Oct 2015 17:18:11 +0000 (UTC) Received: (qmail 16951 invoked by uid 500); 9 Oct 2015 17:18:05 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 16910 invoked by uid 500); 9 Oct 2015 17:18:05 -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 16893 invoked by uid 99); 9 Oct 2015 17:18: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:18:05 +0000 Date: Fri, 9 Oct 2015 17:18:05 +0000 (UTC) From: "Eric Newton (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (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:all-tabpanel ] Eric Newton resolved ACCUMULO-4023. ----------------------------------- Resolution: Cannot Reproduce Fix Version/s: (was: 1.6.5) (was: 1.7.1) (was: 1.8.0) I was unable to reproduce the problem. Code inspection of all points at which namespaces are reserved, here are only 3 places which create a write lock: creating, deleting and renaming the namespace. Created ACCUMULO-4024 so users can determine the state of their namespace locks directly. > 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)