Investigate the feasibility of taking a checkpoint when WT_SESSION.alter returns EBUSY during startup recovery

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is a follow-up server ticket from the conversations held in WT-7902.

      During startup recovery, if the table logging settings need to be changed, there's a chance for WT_SESSION.alter to return EBUSY even if that command is executed after the recovery (see WT-7902 for more details), causing startup to fail. A workaround that was proposed is to take a checkpoint and retry the call when EBUSY is returned. We should investigate the feasibility of this.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Gregory Wlodarek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: