-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Querying, Replication
-
None
-
Fully Compatible
-
ALL
-
Query 2017-01-23
-
0
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.