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

Unify how mongos and mongod default RWC caches handle deleted defaults document

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2020-01-13

      Mongos periodically refreshes its default read write concern cache and will only replace the current defaults in the cache if the found defaults have a greater epoch. If the defaults document is deleted (or the config.settings collection is dropped), the refresh will return a default constructed RWConcernDefault, which has no epoch, so the cache will not be updated.

      In contrast, on mongod the defaults are currently updated through a WUOW onCommit handler, and the cached defaults will be set to whatever the new document is parsed as, which would be a default constructed RWConcernDefault for a delete.

      These behaviors should be unified. Either mongod can ignore the deleted defaults like mongos, or mongos can be made to pick up the deleted defaults.

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: