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

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Won't Do
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              gregory.wlodarek@mongodb.com Gregory Wlodarek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: