accumulo-notifications mailing list archives

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

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

Mime
View raw message