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

Ensure database refreshes are performed after ShardingState initialization

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • Hide
      Show
      Add a mongo::sleepsecs(3) just after _initFunc and the set of the sharding state . Run jstests/core/txns/read_concerns.js on the logical_session_cache_sharding_100ms_refresh_jscore_txns_passthrough suite. You will hit this invariant while trying to run forcePrimaryDatabaseRefreshAndWaitForReplication
    • Sharding 2020-10-05
    • 65

      Commands that requires sharding infrastructure to run will be executed only after Grid::setShardingInitialized() is called, the problem is that by that time the shardingState is not already being initialized. Commands that triggers refreshes of the CatalogCache, will trigger this invariant while trying to run forcePrimaryDatabaseRefreshAndWaitForReplication.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: