[
https://issues.apache.org/jira/browse/ACCUMULO-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950307#comment-14950307
]
marco polo commented on ACCUMULO-4023:
--------------------------------------
John,
yeah, makes sense. We jumped into the code after we saw delete rows on one
table blocking compactions that were running against another. When the delete
op finished the compactions ran. After speaking with 'The Newton,' I've moved
it up to critical.
> 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
> Priority: Critical
> Fix For: 1.7.1
>
>
> 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, we could change
> the path to be ztable_lock/namespaceId/tableId.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
