Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2691

AlterTable transactions should anchor their ops in the WAL

Agile BoardAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.9.0
    • Fix Version/s: None
    • Component/s: consensus, log, tablet
    • Labels:
      None

      Description

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mpercy Mike Percy

              Dates

              • Created:
                Updated:

                Issue deployment