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

AlterTable transactions should anchor their ops in the WAL

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.9.0
    • None
    • consensus, log, tablet
    • 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

          is related to

          Bug - A problem which impairs or prevents the functions of the product. KUDU-860 AlterSchema should log its success or failure in the COMMIT message

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              mpercy Mike Percy
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: