Don't permit enabling or disabling of logging on a mongodb collection if there is a live restore in progress with >0 background threads

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Persistence
    • ALL
    • 8
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Due to live restore workers opening a cursor on a whatever collection they are migrating, enabling or disabling logging causes the mongod to crash.

      Changing the state of logging on a given collection requires exclusive access, the background thread intentionally prevents this behaviour. Now for restore purposes the flag wiredTigerSkipTableLoggingChecksOnStartup prevents this behaviour but I can foresee on prem customers and developers running into this crash scenario.

      The solution here, I think is to log a good error message and still crash or bubble up an error code to the caller or the log enable code path.

      I don't know how practical it will be to check the relevant live restore state.

              Assignee:
              Unassigned
              Reporter:
              Luke Pearson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: