accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4553) DeleteTable repo not replayable
Date Fri, 03 Feb 2017 18:01:02 GMT


John Vines commented on ACCUMULO-4553:

I mean, it probably goes back several years, so I don't think it's urgent since it's not a

> DeleteTable repo not replayable
> -------------------------------
>                 Key: ACCUMULO-4553
>                 URL:
>             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

View raw message