Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-59147

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

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

      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:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: