[jira] [Updated] (ACCUMULO-4023) Table Ops appear to lock namespace and block other table ops
[ https://issues.apache.org/jira/browse/ACCUMULO-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo updated ACCUMULO-4023: - Priority: Critical (was: Major) > 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)
[jira] [Updated] (ACCUMULO-4023) Table Ops appear to lock namespace and block other table ops
[ https://issues.apache.org/jira/browse/ACCUMULO-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo updated ACCUMULO-4023: - Fix Version/s: 1.7.1 > 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 > 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)
[jira] [Updated] (ACCUMULO-4023) Table Ops appear to lock namespace and block other table ops
[ https://issues.apache.org/jira/browse/ACCUMULO-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo updated ACCUMULO-4023: - Description: 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. (was: 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. ) > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACCUMULO-4023) Table Ops appear to lock namespace and block other table ops
[ https://issues.apache.org/jira/browse/ACCUMULO-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo updated ACCUMULO-4023: - Description: 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. (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 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. ) > 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 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)
