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

Move potentially expensive operations out of WT shutdown

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Storage Engines
    • 5

      Potentially expensive operations are done during WT shutdown, but by that point gathering storage engine statistics for ftdc is no longer possible, making diagnosis of problems encountered during shutdown in the field difficult or impossible.

      Since we already trigger the normal checkpoints in the integration layer, could we also do the final checkpoint there?

      That's certainly possible, but it's a non-trivial architectural change. I'd be hesitant to make it at this stage in the 4.4 release but would be happy to explore in depth after the 4.4.0 release.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: