[ACCUMULO-4575] Concurrent table delete operations leave orphan fate transaction locks

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.7.2
• Fix Version/s: 1.7.3, 1.8.1, 2.0.0
• Component/s: fate, master
• Assignee: Keith Turner
• Reporter: Ed Coleman
• Created: 24/Jan/17 05:50
• Updated: 03/Feb/17 05:22
• Resolved: 27/Jan/17 01:11

Description

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.

Issue Links

• is related to: ACCUMULO-4578 Cancel compaction FATE operation does not release namespace lock
• relates to: ACCUMULO-4553 DeleteTable repo not replayable
• links to: GitHub Pull Request #206
• links to: GitHub Pull Request #208