accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4575) Concurrent table delete operations leave orphan fate transaction locks
Date Wed, 25 Jan 2017 16:44:26 GMT


Keith Turner commented on ACCUMULO-4575:

While working on this issue, I have come the conclusion that it is a broader problems.   Its
not just concurrent delete table operations, its fate operations in general running concurrently
with a delete table op.  I think a compact operation started while a delete table op is running
could also have problems getting the namespace id.  I think all FATE operations should resolve
the namespace id once before starting the fate op.

> Concurrent table delete operations leave orphan fate transaction locks
> ----------------------------------------------------------------------
>                 Key: ACCUMULO-4575
>                 URL:
>             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: 1.5h
>  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

View raw message