You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2019/02/08 19:39:00 UTC

[jira] [Updated] (KUDU-2691) AlterTable transactions should anchor their ops in the WAL

     [ https://issues.apache.org/jira/browse/KUDU-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Percy updated KUDU-2691:
-----------------------------
    Component/s: consensus

> AlterTable transactions should anchor their ops in the WAL
> ----------------------------------------------------------
>
>                 Key: KUDU-2691
>                 URL: https://issues.apache.org/jira/browse/KUDU-2691
>             Project: Kudu
>          Issue Type: Bug
>          Components: consensus, log, tablet
>    Affects Versions: 1.9.0
>            Reporter: Mike Percy
>            Priority: Major
>
> AlterTable does not appear to anchor its WAL ops, meaning there is nothing preventing Kudu from GCing a WAL segment including an AlterTable that is running very slowly for some reason. If that happens and then the tserver is killed, it's possible for that replica to fail to start back up later. We should anchor alter ops in the same way we anchor write operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)