Mongos SRV Poller shouldn't start until 60 seconds after the client is first created

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor - P4
    • 4.7
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      The Mongos SRV Poller (SrvMonitor) shouldn't start until 60 seconds after the client is first created as discussed in HELP-36687:

      Yes, however, what confuses me is that it all happens within a couple of seconds since the MongoClient was instantiated since the added endpoints were removed. I thought the driver won't be querying the DNS faster than 1 every 60 seconds.

      Ah I see, when PyMongo discovers the topology as sharded (after the first heartbeat response), it starts the SrvMonitor thread. The SrvMonitor thread runs the SRV polling lookup immediately and then sleeps for 60 seconds. Perhaps we want to delay the first SRV polling lookup by 60 seconds.

              Assignee:
              Noah Stapp
              Reporter:
              Shane Harvey
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: