You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2018/10/23 21:03:00 UTC
[jira] [Assigned] (KUDU-1678) Race during abort of pending
operations during raft shutdown
[ https://issues.apache.org/jira/browse/KUDU-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will Berkeley reassigned KUDU-1678:
-----------------------------------
Assignee: Will Berkeley
> Race during abort of pending operations during raft shutdown
> ------------------------------------------------------------
>
> Key: KUDU-1678
> URL: https://issues.apache.org/jira/browse/KUDU-1678
> Project: Kudu
> Issue Type: Bug
> Components: consensus
> Affects Versions: 1.0.0, 1.6.0, 1.8.0
> Reporter: Todd Lipcon
> Assignee: Will Berkeley
> Priority: Major
> Attachments: alter_table-randomized-test-debug.log.xz, alter_table-randomized-test-release.log.xz
>
>
> I'm seeing the following race occasionally in alter_table-randomized-test:
> - a follower tablet is shutting down while some operations are pending. The first operation is an ALTER_TABLE, and the second is a WRITE which depends on the ALTER (i.e includes the new column)
> - we cancel the ALTER successfully, and then the thread gets de-scheduled
> - the PrepareTask for the WRITE runs before we're able to cancel it. It then fails to prepare because the alter it depends on has not completed
> It seems like we should probably cancel the pending operations in reverse order.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)