[jira] [Comment Edited] (ACCUMULO-4553) DeleteTable repo not replayable

["John Vines (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851733#comment-15851733 ] 

John Vines edited comment on ACCUMULO-4553 at 2/3/17 5:03 PM:
--------------------------------------------------------------

Nothing in the PRs for ACCUMULO-4575 addressed this issue, nor does pr 204


was (Author: vines):
Nothing in the PRs for ACCUMULO-4575 addressed this issue

> DeleteTable repo not replayable
> -------------------------------
>
>                 Key: ACCUMULO-4553
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4553
>             Project: Accumulo
>          Issue Type: Bug
>          Components: fate, master
>    Affects Versions: 1.6.6, 1.7.2
>            Reporter: John Vines
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>
>
> I had an issue where a table was stuck in a deleting state. I'm still digging into the specifics of the incident, but I'm looking at the DeleteTable repo and it does not seem safe to replay if the master goes down during execution. It calls TableManager.transitionTableState which does a zk mutation that does not allow Deleting->Deleting. This means that if the repo dies after the mutation but before seeding the next fate repo, any repeats will fail due to it already being in a deleting state.
> Furthermore, the only way to correct this behavior is to manually force the table into a non-deleting state via zk surgery, and no one wants that.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)