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

geo_s2cursorlimitskip.js fails in initial sync passthrough due to reads performed by the repl system

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.2, 3.5.2
    • Querying, Replication
    • None
    • Fully Compatible
    • ALL
    • Query 2017-01-23
    • 0

    Description

      The geo_s2cursorlimitskip.js test makes assertions about the number of query and getMore operations performed against a particular collection. This is invalid in our initial sync passthrough suite, core_small_oplog_rs_initsync. When an initial sync occurs during the execution of the test, the downstream node will issue a find command against its sync source in order to clone the data. From the sync source's perspective, this read looks just like any user-issued find, and it will be counted by the operation latency histogram. This causes the read count to be higher than expected by the test.

      Attachments

        Activity

          People

            james.wahlin@mongodb.com James Wahlin
            james.wahlin@mongodb.com James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: