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

Account for the time mongos takes to update config server

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sharding NYC
    • Fully Compatible
    • ALL
    • Sharding NYC 2023-10-16
    • 35

      In repl_monitor_refresh.js, we start a sharding test with 1 shard that specifies 3 nodes. With auto-bootstrap, there is an auto initialization in the beginning which makes it necessary to be a reconfig when there are particular setting specified(like number of nodes). Mongos needs to update the config server on a topology state change so change the assert here to be an assert.soon in the case that mongos is a bit slow triggering the update. 

            Assignee:
            kruti.shah@mongodb.com Kruti Shah
            Reporter:
            kruti.shah@mongodb.com Kruti Shah
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: