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 2016/10/04 20:48:20 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15546615#comment-15546615 ] 

Todd Lipcon commented on KUDU-1678:
-----------------------------------

Extracted the interesting bits of the log here: https://gist.github.com/fc61d13442215b586bc20be4fb5b7e5e

> 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
>            Reporter: Todd Lipcon
>
> 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
(v6.3.4#6332)