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

Ensure "new Mongo(...)" is connected to the node

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Correctness
    • Fully Compatible
    • 2025-03-04
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      A bunch of resmoke hooks (but probably not only hooks) are not able to connect to the node in BF-20010. Some particular lines where it fails, but most likely not the full list:
      https://github.com/10gen/mongo/blob/aabc1a93d2167a4ac5b60adc4cc733a45f4625e4/jstests/hooks/run_validate_collections_background.js#L60
      https://github.com/10gen/mongo/blob/1c0abd198776e4da356ff1483ce444e762a012fd/jstests/hooks/run_dbcheck_background.js#L32
      https://github.com/10gen/mongo/blob/89dd69676156c78fde985f0105b82a9b32db0dc7/jstests/hooks/validate_collections.js#L138

      Possible fixes:

      1. Retry "new Mongo(...)" in case of connections errors
      2. Increase the connection timeout for "new Mongo(...)"

            Assignee:
            eric.lavigne@mongodb.com Eric Lavigne
            Reporter:
            mikhail.shchatko@mongodb.com Mikhail Shchatko
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: