[
https://issues.apache.org/jira/browse/ACCUMULO-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wall updated ACCUMULO-4575:
-----------------------------------
Fix Version/s: (was: 1.8.2)
1.8.1
> Concurrent table delete operations leave orphan fate transaction locks
> ----------------------------------------------------------------------
>
> Key: ACCUMULO-4575
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4575
> Project: Accumulo
> Issue Type: Bug
> Components: fate, master
> Affects Versions: 1.7.2
> Reporter: Ed Coleman
> Assignee: Keith Turner
> Priority: Minor
> Fix For: 1.7.3, 1.8.1, 2.0.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> There is an issue where orphan zookeeper transaction locks (as reported by
> the FATE print command) are being created if delete commands are issued for
> the same table concurrently.
> The DELETE fate transaction does not keep track of the table id and when one
> of the delete operations succeeds, any others queued throw an exception
> because the table does not exist any more - this causes the existing
> zookeeper transaction locks to become orphaned and they required manual
> clean-up.
> This may be related to ACCUMULO-4553.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
