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

[v4.0] Log start and end of changes to table log settings

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 4.0.22
    • 4.0.23
    • Diagnostics
    • None
    • Fully Compatible
    • v4.4, v4.2, v4.0
    • Execution Team 2021-02-08

    Description

      Under some circumstances we can change the table log (journaling) settings of every table on startup, and this can take a long time if the user has a lot of tables. This occurs in particular in conjunction with enableReadConcerMajority settings. We should log the start and end of this activity so that users and MongoDB support know why startup is slow.

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. SERVER-53247 Disable enableMajorityReadConcern:false

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-43664 Speedup WiredTiger storage engine startup for many tables by optimizing WiredTigerUtil::setTableLogging()

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              gregory.wlodarek@mongodb.com Gregory Wlodarek
              bruce.lucas@mongodb.com Bruce Lucas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: