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

Get rid of all non-metadata usages of DBConfig::isShardingEnabled

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.2, 3.5.2
    • Affects Version/s: 3.5.1
    • Component/s: Sharding
    • None
    • Fully Compatible
    • v3.4
    • Sharding 2017-01-02

      The DBConfig::isShardingEnabled function should only be called for metadata commands which want to prevent operations form happening on non-sharding enabled database. The only two such commands are copydb and shardCollection. All other usages should be removed.

      Also, the DBConfig::getAllShardedCollections function is only used in the database-wide metadata commands movePrimary and dropDatabase. Since these commands must always run with a fully up-to-date metadata, there is no point in them using the cached collections list so DBConfig::getAllShardedCollections is unnecessary and should be removed.

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

              Created:
              Updated:
              Resolved: