accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-4023) Table Ops appear to lock namespace and block other table ops
Date Fri, 09 Oct 2015 17:18:05 GMT

     [ 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)

Mime
View raw message