You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/03/22 17:37:00 UTC
[jira] [Assigned] (KUDU-2109)
TabletCopyClientSessionITest.TestCopyFromCrashedSource is flaky
[ https://issues.apache.org/jira/browse/KUDU-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon reassigned KUDU-2109:
---------------------------------
Assignee: Todd Lipcon
> TabletCopyClientSessionITest.TestCopyFromCrashedSource is flaky
> ---------------------------------------------------------------
>
> Key: KUDU-2109
> URL: https://issues.apache.org/jira/browse/KUDU-2109
> Project: Kudu
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.4.0
> Reporter: Adar Dembo
> Assignee: Todd Lipcon
> Priority: Major
> Attachments: 0_tablet_copy_client_session-itest.txt
>
>
> I've attached the full log from my test failure.
> I think I've found the issue too: the test assumes that if it finds an on-disk superblock in the TOMBSTONED state, the failed tablet copy has finished and it's safe to start another one. However, in TSTabletManager::RunTabletCopy, 'tc_client' goes out of scope before 'deleter', which means that the TabletCopyClient destructor (which deletes the on-disk data, flushing the superblock in the TOMBSTONED state) will run before the TransitionInProgress destructor (which removes the tablet's ID from the global map tracking transitions, allowing a new tablet copy to proceed).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)