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

Remove double loading of the sharding database metadata entry

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • 3.4.0, 3.5.1
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-01-02, Sharding 2017-02-13, Sharding 2017-03-06

    Description

      The sharding cache currently loads the database metadata entry twice - once as part of the cache check and once when the entire DBConfig is loaded. This is not necessary and also prevents some of the fields from being marked as const, specifically _primaryId.

      Since we have no means of forcing the refresh of a database primary, there is no point in reloading this value each time we force reload of the collections in DBConfig::reload.

      Attachments

        Issue Links

          Activity

            People

              kaloian.manassiev@mongodb.com Kaloian Manassiev
              kaloian.manassiev@mongodb.com Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: