You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2017/04/06 21:45:41 UTC

[jira] [Updated] (KUDU-1607) Unable to delete FAILED tablets as part of drop table

     [ https://issues.apache.org/jira/browse/KUDU-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated KUDU-1607:
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0
                   1.3.1
           Status: Resolved  (was: In Review)

> Unable to delete FAILED tablets as part of drop table
> -----------------------------------------------------
>
>                 Key: KUDU-1607
>                 URL: https://issues.apache.org/jira/browse/KUDU-1607
>             Project: Kudu
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.10.0
>            Reporter: Dan Burkert
>            Assignee: Mike Percy
>             Fix For: 1.3.1, 1.4.0
>
>
> When dropping a table with a failed tablet, the tablet will fail to be deleted. The /tablets endpoint shows its Last Status as: {{Invalid argument: Unable to delete on-disk data from tablet 2e3b95dba81044748a9a52eb138dd59c: The metadata for tablet 2e3b95dba81044748a9a52eb138dd59c still references orphaned blocks. Call DeleteTabletData() first}}
> Steps to repro:
> 1. Create a table with a single tablet, single replica.
> 2. Load enough data to have the WAL roll a segment
> 3. Corrupt the magic bytes of a non-current segment
> 4. Restart the TS
> 5. Drop the table



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