[jira] [Updated] (KUDU-1554) Tombstoned replicas remain on TS even after table is deleted
[ https://issues.apache.org/jira/browse/KUDU-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-1554: -- Target Version/s: (was: 1.5.0) > 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: 1.2.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 (v7.6.3#76005)
[jira] [Updated] (KUDU-1554) Tombstoned replicas remain on TS even after table is deleted
[ https://issues.apache.org/jira/browse/KUDU-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-1554: -- Affects Version/s: (was: 0.10.0) 1.2.0 Target Version/s: 1.4.0 The above-mentioned "still references orphaned blocks" was spotted again in the wild on 1.2. > 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: 1.2.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.15#6346)
