[jira] [Commented] (KUDU-1554) Tombstoned replicas remain on TS even after table is deleted

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon commented on KUDU-1554:
-----------------------------------

I restarted the master in this cluster (without restarting the tservers) and now am getting a lot of spew of the following:
W0811 14:25:10.911065 36475 catalog_manager.cc:2522] TS 7cd4ef9ab9884aca8d78bb458f60e499: delete failed for tablet 9fca7aee7d9349b7aec58b301c64b817 with error code UNKNOWN_ERROR: Invalid argument: Unable to delete on-disk data from tablet 9fca7aee7d9349b7aec58b301c64b817: The metadata for tablet 9fca7aee7d9349b7aec58b301c64b817 still references orphaned blocks. Call DeleteTabletData() first

> Tombstoned replicas remain on TS even after table is deleted
> ------------------------------------------------------------
>
>                 Key: KUDU-1554
>                 URL: https://issues.apache.org/jira/browse/KUDU-1554
>             Project: Kudu
>          Issue Type: Bug
>          Components: master, tserver
>    Affects Versions: 0.10.0
>            Reporter: Todd Lipcon
>            Priority: Minor
>
> If a replica is deleted on a live table, a tombstone replica is left with TABLET_DATA_TOMBSTONED state. If the table is then deleted, those tombstones aren't cleaned up, and will remain on the tserver until the next time the tserver restarts.
> Not a big deal, but it may be confusing to users to see these tombstones sticking around.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)