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

sharding read_after_optime.js test timeout should exceed ping interval

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • None
    • 3.2.4, 3.3.3
    • Sharding
    • Fully Compatible
    • ALL
    • 0

    Description

      The balancer continually updates the config server. The interval used by the balancer needs to be taken in account when choosing an appropriate readConcern timeout for the test.

      To reproduce, change the maxTimeMS in this line from 5000 ms to some value larger than the ping interval (10 secs):

          var runFindCommand = function(ts) {
              return primaryConn.getDB('local').runCommand({
                  find: 'oplog.rs',
                  readConcern: {
                      afterOpTime: {
                          ts: ts,
                          t: term,
                      },
                  },
                  maxTimeMS: 5000, <- change to 20000
              });
          };
      

      Attachments

        Activity

          People

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: