[
https://issues.apache.org/jira/browse/KUDU-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930735#comment-15930735
]
Mike Percy commented on KUDU-1607:
----------------------------------
I just reproduced this in a slightly different way:
1. Load too much data and fill up disks.
2. Kudu crashes because unable to write.
3. Restart Kudu, tablet bootstrap fails because of fill disk and tablet ends up
in FAILED state.
4. Drop table / Attempt to delete tablet: fails with the message:
W0317 13:05:19.324373 13242 ts_tablet_manager.cc:634] Invalid argument: Unable
to delete on-disk data from tablet d1b857ddaa0743c79c9bcbd9b2fda174: The
metadata for tablet d1b857ddaa0743c79c9bcbd9b2fda174 still references orphaned
blocks. Call DeleteTabletData() first
> 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
>
> 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)
