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

Add tests to check that mongos marks a mongod as failed in failure cases

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.0-rc3, 4.7.0
    • Sharding
    • None
    • Fully Compatible
    • v4.4
    • Sharding 2020-04-06, Service arch 2020-04-20, Service arch 2020-05-04

    Description

      Add the following three test cases to check that mongos correctly marks a mongod as down (marks its type as unknown in its server description):

      1. After mongos receives one isMaster response from a node, cease all isMaster replies on this node. MongoS should mark this node as down after connectTimeoutMS + maxAwaitTimeMS.
      2. After mongos receives one isMaster response from a node, kill the node.
      3. After mongos receives one isMaster response from a node, make mongod respond with 'ok : 0' in all future isMaster replies.

      Add a fourth test case to check that mongos does not mark a mongod as down if mongod responds with 'ok : 1' but without the 'moreToCome' bit set. This test should verify that the client does not mark the server unknown and continues monitoring the mongod after it ends the isMaster stream.

      Attachments

        Issue Links

          Activity

            People

              janna.golden@mongodb.com Janna Golden
              janna.golden@mongodb.com Janna Golden
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: