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 A1ECD18C16 for ; Thu, 8 Oct 2015 17:06:45 +0000 (UTC) Received: (qmail 33403 invoked by uid 500); 8 Oct 2015 17:06:27 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 33320 invoked by uid 500); 8 Oct 2015 17:06:27 -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 32948 invoked by uid 99); 8 Oct 2015 17:06:27 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2015 17:06:27 +0000 Date: Thu, 8 Oct 2015 17:06:27 +0000 (UTC) From: "marco polo (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-4023?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo updated ACCUMULO-4023: --------------------------------- Description: I've noticed table repeatable operations impacting other t= able 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 nam= espace and tables, it seems as though in most cases we only want a table lo= ck, we could change the path to be ztable_lock/namespaceId/tableId. (was:= I've noticed table repo operations impacting other table ops. Upon looking= at the code it appears as though we reserve the name space, attempt to loc= k it, and then lock the table. Someone more familiar with the code can debu= nk me, but it appears as though we're blocking table ops on alternate table= s. 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, we could change th= e path to be ztable_lock/namespaceId/tableId. ) > 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: Improvement > Affects Versions: 1.6.4 > Reporter: marco polo > > 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 c= an debunk me, but it appears as though we're blocking table ops on alternat= e tables. The same code for getting the lock is used for namespace and tabl= es, it seems as though in most cases we only want a table lock, we could ch= ange the path to be ztable_lock/namespaceId/tableId.=20 -- This message was sent by Atlassian JIRA (v6.3.4#6332)